# Seeds 🌱

*A skill to share context quickly between agents*

Published 2026-04-30 · https://dom.vin/2026/seeds

## Summary

The seed skill is a way for agents to share context — bundles of files (memory, skills, plans) wrapped in a folder. Install once with `Fetch & install seed.show/skill`. Tell your agent to share any folder and it gives you back a URL; the recipient pastes the URL into their agent and the files land locally, context shared. The essay frames this as the smallest end of a much bigger spectrum: dyadic context-building, small-group shared lore, civilizational moral-constitution context. Same dynamics rhyme at every scale; texture and stakes change. Seeds is the small case — one folder, one prompt, one URL — and the small case being good enough is what's been missing. Built on fold (folder ↔ single markdown file) and portdown (markdown ↔ self-installing polyglot).

## Claims

- Markdown has become the language of AI context — memory, skills, plans, resources all end up as bundles of markdown wrapped in a folder.
- Sharing those bundles between agents is the friction; seeds is the smallest-case answer to it.
- Context-sharing is a spectrum — dyadic, small-group, civilizational — and the small end being good enough is what's been missing.

---

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 files or folders using a short url. A no-friction transport layer for agent context:

<InstallBox
  phrase="Fetch & install seed.show/skill"
  scriptUrl="https://seed.show/skill"
/>

<SeedScene id="seed-handoff" description={`Two chat panels with the seed pill floating between them, framed throughout by faint hand-drawn pencil outlines that show where every element will land before it appears. Top panel labelled 'publisher', four turns: Dom pastes 'Fetch & install seed.show/skill' to install the skill itself; the agent confirms 'Seed skill installed'; Dom then says 'Share /review-draft, ask for feedback'; the agent replies '🚀 seed.show/xkot0'. Between the two panels: a sage-green URL pill 'seed.show/xkot0' (the hero of the figure, glowing once), with a soft pulsing glow and eight radial rays. Bottom panel labelled 'recipient': a friend's message bubble (right-aligned) shows the pasted 'Fetch & install seed.show/xkot0'; below it, a folder card '/tmp/seed-xkot0/' with three file rows (README.md, intro.md, outline.md) — the install result; then the agent's reply (sage-tinted, left-aligned): 'Downloaded /review-draft. You've been asked for feedback.' The argument: install the skill once, then any folder becomes a URL the recipient can paste. By the rest state every element has filled in and the figure 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](https://github.com/openclaw/openclaw) built its memory from a handful of markdown files. Karpathy proposes a [markdown wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f) of your life. Skills are [bundles of markdown](https://www.anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills) 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](https://dom.vin/fold) and [portdown](https://dom.vin/portdown), small agent-first bash utilities you can install separately if you're shipping your own context-shaped thing.