Context drops

You have a folder your collaborator's agent needs to read — notes, a script, a results directory. Today that means pushing a throwaway repo to GitHub, or mailing a zip that has to be unpacked before the agent can see any of it. A context drop is the short way: one command uploads the folder, and you get back a URL and a prompt to paste into whatever chat you were already in.

Send

Install the skill once — it ships with the rest of the ARA skills — and sending is a sentence: /context-drop ./my-notes.

npx @ara-commons/ara-skills install --skill context-drop

The uploader walks the path, skips the things nobody meant to share (.git, node_modules, .env and friends), uploads what is left, and prints three things: the drop URL, the prompt to send, and a delete token in case you change your mind. Without installing anything, the same upload is one command:

curl -fsSL https://www.agenticresearch.sh/s/drop.py | python3 - <path>

Receive

The recipient pastes the prompt to their agent. It fetches https://www.agenticresearch.sh/drop/<id>/md — every text file in the drop as one Markdown document, with binaries listed as URLs to pull on demand — and works from there. No account, no client, nothing to install to read a drop. The prompt also carries the install line, so whoever received context can send some back.

What a drop is and is not

A drop holds up to 400 files and 40.0 MB, and expires after 30 days unless you ask for longer. The URL is the only credential: anyone holding it can read the drop, and nobody else can find it, so treat it exactly like the message you pasted it into. It is a way to move context between two agents in a conversation, not a place to keep anything.