Agents accumulate context over time. Memories, skills, plans, artifacts. They’re all bundles of markdown, sometimes a bit of code.
This skill lets agents share context using a short url. Files or folders. A no-friction transport layer for agent context:
Three vertical zones, framed throughout by faint hand-drawn pencil outlines that show where every element will land before it appears. Zone one (top): a chat panel labelled 'publisher'. The user's message bubble (right-aligned) reads 'share review-draft, ask for feedback'. Below it, the agent's reply (sage-tinted, left-aligned) reads '🌱 Fetch & install seed.show/xkot0'. Zone two (middle): the mechanism. A folder card labelled 'review-draft/' with three file rows (README.md, intro.md, outline.md) sits at the top. A small downward arrow labelled 'seed plant' leads to a sage-green URL pill — 'seed.show/xkot0', the hero of the figure, glowing once. A second arrow labelled 'Fetch & install' leads down to an identical folder card now labelled '/tmp/seed-xkot0/' with the same three files. Zone three (bottom): a chat panel labelled 'recipient'. The user's message bubble (right-aligned) shows the pasted '🌱 Fetch & install seed.show/xkot0'. The agent's reply below (sage-tinted, left-aligned) reads 'This is a review draft. You've been asked for feedback.' The argument is that the URL is the entire affordance — the user just types 'share', the recipient just pastes; the mechanism in the middle is what the URL hides. By the rest state every zone has filled in and the conversation reads top to bottom as a single handoff.
Three vertical zones, framed throughout by faint hand-drawn pencil outlines that show where every element will land before it appears. Zone one (top): a chat panel labelled 'publisher'. The user's message bubble (right-aligned) reads 'share review-draft, ask for feedback'. Below it, the agent's reply (sage-tinted, left-aligned) reads '🌱 Fetch & install seed.show/xkot0'. Zone two (middle): the mechanism. A folder card labelled 'review-draft/' with three file rows (README.md, intro.md, outline.md) sits at the top. A small downward arrow labelled 'seed plant' leads to a sage-green URL pill — 'seed.show/xkot0', the hero of the figure, glowing once. A second arrow labelled 'Fetch & install' leads down to an identical folder card now labelled '/tmp/seed-xkot0/' with the same three files. Zone three (bottom): a chat panel labelled 'recipient'. The user's message bubble (right-aligned) shows the pasted '🌱 Fetch & install seed.show/xkot0'. The agent's reply below (sage-tinted, left-aligned) reads 'This is a review draft. You've been asked for feedback.' The argument is that the URL is the entire affordance — the user just types 'share', the recipient just pastes; the mechanism in the middle is what the URL hides. By the rest state every zone has filled in and the conversation reads top to bottom as a single handoff.
Motivation
I love Markdown. Plain text first, structure second; a human eye, a machine pass, respecting both readers. Copy and paste to share. A perfectly portable packet of structured thought.
Markdown has become the language of AI context. OpenClaw built its memory from a handful of markdown files. Karpathy proposes a markdown wiki of your life. Skills are bundles of markdown that teach agents how to do agent things.
Multiple files makes sense for these bundles. They’re designed for agents to edit and maintain; agents work better within a clear structure. They’re just a little harder to share. Zip, upload, unzip.
Context, more broadly, is a spectrum. Two people building common ground in a chat. A small team carrying the same picture of a project. A tribe holding shared lore. A civilisation accumulating a moral constitution it never wrote down. The same dynamics rhyme at every scale; what changes is the texture and the stakes.
Most agent collaboration today sits at the smallest, simplest end of that spectrum: one folder, one prompt, two agents trading. The thing that’s been missing isn’t the bigger end. It’s the small case being good enough that you’d actually use it.
A seed is the small case. A folder, a one-line note, a URL. The recipient agent reads it the way an apprentice reads a sticky note on top of a stack of papers: here’s what’s here, here’s what to do. No metadata schema, no conjugation, no taxonomy. Just the artifact and the intent, addressable at a URL.
There are bigger versions of this idea. Capture-time metadata that lets context age, expire, supersede itself. Selectively-revealed context, where one party holds a layer the other can’t see. Shared lore at the scale of a community or a culture. Worth essays of their own, in time.
For now, the small case. Files plus next action. The half-written sticky note is what carries the work forward; without it the recipient gets a bag of files and has to guess.
Built on fold and portdown, small bash utilities you can install separately if you’re shipping your own context-shaped thing.