droplisted
Install: claude install-skill lroolle/skills
# drop
A drop is a live, expiring, revocable URL wrapping a bundle of
static files, with a review surface a human can annotate and a
feedback API the agent reads back. It closes the loop that
publish-only tools leave open: publish -> human reviews -> agent
reads structured feedback -> revise -> republish, same link.
The interface is MCP-only: four tools from the drop MCP server.
Configure once:
```json
{
"mcpServers": {
"drop": {
"command": "npx",
"args": ["-y", "@agentdrop/mcp"],
"env": { "AGENTDROP_URL": "https://<your-drop-service>" }
}
}
}
```
## Step 1 -- Gate
Publishing is the exception, not the default exit for every
artifact. Publish when a human other than the requester must see
it, when review needs to happen on another machine or async, or
when an agent loop must block on a human verdict. Stay local when:
| Signal | Route |
|---|---|
| The artifact carries secrets, client code, PII, unreleased work | Keep local -- a capability URL is a publication; treat it like posting the file |
| The requester will review in this same session | Just give the file path; a URL adds nothing |
| The user wants to browse a whole workspace, not one deliverable | docent serves it locally, nothing leaves the machine |
| The deliverable itself still needs building | htmlize first; drop is transport, not authoring |
State what is in the bundle before publishing. If any row above
matches, say which and stop.
## Step 2 -- Publish
Bundle rules: one dire