garden-capture
Skill4 starsChanged 6 months agoMITView on GitHub
Capture a thought, decision, learning, or fact into the garden vault inbox. Use ONLY when the user explicitly asks: "capture X", "remember that X", "for the garden Y", "save this", etc. Do not capture proactively — the user wants to approve what lands in the vault. Writes to ~/garden/inbox/: the gardener will file it properly later.
In this repository4 other files it gives its agents.
- garden-bootstrapSkill
- gardenerSkill
- garden-recallSkill
- garden-voiceSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Only when the user explicitly invokes capture.
- Distinctive: line 36
Write the file. Don't edit anything else in the vault: that's the gardener's job.
- Distinctive: line 42
If the user dumps several distinct things at once, write each as a separate inbox file.
- Very specific: line 46
Don't file directly into notes/, decisions/, etc.: that's gardener territory.
- Distinctive: line 47
Don't add wiki-links speculatively.
- Distinctive: line 48
Don't ask for permission for routine captures.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
garden-capture
Drops a raw capture into ~/garden/inbox/. The gardener (scheduled) processes inbox files into properly-filed atomic notes.
When to use
Only when the user explicitly invokes capture. Triggers: "capture this", "save that", "for the garden", "remember X", or equivalents.
If you notice something in conversation that seems noteworthy but the user didn't ask to capture, do not write to inbox/. Suggest it inline ("worth capturing?") and let the user decide. The vault is the user's, and they want explicit control over what goes in.
How
- Compose a short markdown file with this structure:
---
type: capture
created: <YYYY-MM-DD>
source: <session | manual | conversation>
---
# <one-line summary>
<the content: keep it raw, gardener will refine>
Context: <project | person | topic if known>- Filename:
~/garden/inbox/<YYYY-MM-DD>-<slug>.md. Slug = first 5–7 words of the summary, lowercased, hyphenated. - Write the file. Don't edit anything else in the vault: that's the gardener's job.
- Tell the user one line: "Captured to inbox as
<filename>."
Multiple captures
If the user dumps several distinct things at once, write each as a separate inbox file. One concept per file.
Don't
- Don't file directly into
notes/,decisions/, etc.: that's gardener territory. - Don't add wiki-links speculatively. Gardener handles linking.
- Don't ask for permission for routine captures. Just write.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.