capture-note
Skill0 starsChanged 5 months agoMITView on GitHub
Capture a note into 00-inbox/ with proper frontmatter and at least one wikilink. Use for any text/idea/snippet that should become a durable vault note but doesn't yet have a home.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-extremeSkill
- auditSkill
- capture-taskSkill
- councilSkill
- daily-catchupSkill
- dailySkill
- dreamSkill
- project-scaffoldSkill
- projectSkill
- setupSkill
- weeklySkill
- workspaceSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read input from invocation.
- Distinctive: line 16
If the body is more than one sentence and no clear title is obvious, prompt: *"What's the title?"* Otherwise, infer a short title (≤8 …
- Very specific: line 22
If the user cannot name any related note, ask: *"No related note found.
- Very specific: line 24
Read templates/inbox-note.md and substitute:
- Very specific: line 32
If the file path already exists, append -2, -3, etc.
- Distinctive: line 34
Write the file. Report path and wikilinks added.
- Very specific: line 38
Never write a note with zero wikilinks unless the user explicitly accepted the #orphan fallback.
- Distinctive: line 40
Never overwrite an existing file.
- Very specific: line 41
Use [[wikilinks]], never markdown links.
≈ “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
Capture-Note Skill
What this does
Writes a new note to 00-inbox/YYYY-MM-DD-<slug>.md with full frontmatter, the body the user provided, and at least one [[wikilink]] to a related existing vault note.
Steps
- Read input from invocation. If invoked as
/capture-note <text>, the text is the body. If invoked with no arg, prompt: "What's the note? Paste the text." - If the body is more than one sentence and no clear title is obvious, prompt: "What's the title?" Otherwise, infer a short title (≤8 words) from the first sentence.
- Slugify the title: lowercase, replace spaces with hyphens, strip non-alphanumerics. Compute today's date
YYYY-MM-DD. Compute the path00-inbox/{{date}}-{{slug}}.md. - Prompt: "What does this relate to? Name at least one existing vault note (e.g.,
[[some-related-note]]). You can search the vault first." Accept a list. For each name given, verify the note exists via Glob/Grep. If no matches, ask again with the list of suggestions. - If the user cannot name any related note, ask: "No related note found. Tag this as
#orphanand proceed?" Ony, set tags to[inbox, orphan]andrelated:to[]. Onn, stop and report. - Read
templates/inbox-note.mdand substitute:{{date}}→ today's date{{source}}→"/capture-note"{{related-wikilinks}}→ YAML list of wikilinks, e.g.,["[[note-a]]", "[[note-b]]"]{{title}}→ the title{{body}}→ the user's text{{related-list}}→ bulleted list of wikilinks
- If the file path already exists, append
-2,-3, etc. to the slug until unique. Report the rename to the user. - Write the file. Report path and wikilinks added.
Rules
- Never write a note with zero wikilinks unless the user explicitly accepted the
#orphanfallback. - Tags come from
_meta/tags.mdapproved vocabulary. If the user requests a new tag, add#flag-tagand tell them to update_meta/tags.md. - Never overwrite an existing file. Auto-rename on collision.
- Use
[[wikilinks]], never markdown links. - Frontmatter
source:field is always"/capture-note"for audit.
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.

