capture-to-vault
Skill3 starsChanged 51 days agoMITView on GitHub
Use during /research, /scope (or any recipe) to write or update a vault note via dossier-mcp. Agent drafts slug + frontmatter + body + citations, writes the note, and surfaces what was captured so the user can redirect afterward. Supports create (new note) and update (refine existing note) modes.
In this repository8 other files it gives its agents.
- agent-reviewSkill
- cleanup-artifactsSkill
- dispatch-explorationSkill
- load-contextSkill
- open-draft-prSkill
- plan-fileSkill
- publish-prSkill
- repo-setupSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
If parent_slug is supplied: <parent_slug>/<topic-slug>.
- Distinctive: line 36
Draft the body: Ensure:
- Very specific: line 40
If citations present: include a ## Sources section at the end listing each citation (title — URL — accessed date)
- Very specific: line 42
Write the note: Call mcp__dossier-mcp__create_note with the draft.
- Very specific: line 52
Read the existing note: Call mcp__dossier-mcp__get_note with the supplied slug to load its current frontmatter and body.
- Very specific: line 57
If new tags emerge from the new content, merge them into existing tags (no duplicates).
- Very specific: line 60
If citations present: integrate into the existing ## Sources section if there is one, or add one.
- Very specific: line 62
Write the note: Call mcp__dossier-mcp__update_note with the updated content.
- Distinctive: line 74
Lead with the conclusion: if there is one.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 to Vault
Draft a note and write it. Surface the slug and any non-obvious placement decisions afterward so the user can redirect or revise. Do not wait for approval before writing. One note per call.
Modes
- create (default) — write a new vault note via
mcp__dossier-mcp__create_note. - update — refine an existing note in place via
mcp__dossier-mcp__update_note. Preserves required frontmatter and auto-bumps theupdated:field.
Input
mode(optional) —create(default) orupdate.body— the finding, decision, or synthesis. Markdown. Lead with the conclusion or key takeaway. In update mode, this represents the intended new state of the body (or a description sufficient to derive it from the loaded current state).slug(required for update mode) — the existing note's slug.related(optional) — vault slugs the note references. If absent, infer from body content and recent session context.citations(optional) — list of{title, url, accessed}entries from web-researcher findings. Include whenever the body draws on web sources.parent_slug(optional, create mode only) — path prefix hint, e.g.projects/relocation. If absent, infer from content and vault structure. Ignored in update mode.
Process — create mode
- Draft the destination slug.
- If
parent_slugis supplied:<parent_slug>/<topic-slug>. - Else: infer from body content and related notes. Place as a sibling to the most relevant related note. Avoid
inbox/unless nothing better fits.
- If
- Draft the frontmatter:
title— readable title derived from the body's main claimdate— today's date (YYYY-MM-DD)tags— 2–4 tags inferred from bodyrelated— the inputrelated(or inferred list)
- Draft the body. Ensure:
- Lead with the conclusion or key takeaway
- Density over readability — pack in conclusions and reasoning, not just facts
- Self-contained — key context inline, not only via links
- If
citationspresent: include a## Sourcessection at the end listing each citation (title — URL — accessed date)
- Write the note. Call
mcp__dossier-mcp__create_notewith the draft. - Backlink. For each slug in
related, callmcp__dossier-mcp__update_noteto add the new note's slug to that note'srelatedfield. Skip if already present. - Surface what was written. Briefly state the created slug and any non-obvious placement decisions (tag choices, parent folder selection). The user can redirect, revise, or ask for edits after the write. If the user redirects, update/move the note rather than abandoning the write.
- Return: the created slug.
Process — update mode
- Read the existing note. Call
mcp__dossier-mcp__get_notewith the suppliedslugto load its current frontmatter and body. - Generate the updated content.
- Preserve all required frontmatter fields from the existing note (
title,date,tags,related, plus any recipe-specific fields likestatusfor scope docs). Do not drop or rename them. - Auto-bump the
updated:field to today's date (YYYY-MM-DD). Add the field if it doesn't exist. - If new tags emerge from the new content, merge them into existing
tags(no duplicates). Do not replace. - Merge any new entries in
relatedwith existing ones (no duplicates). Do not replace. - Compose the new full body — integrate the input
bodyinto the doc as the caller intends. The caller is responsible for handing you a body that represents the desired new state. - If
citationspresent: integrate into the existing## Sourcessection if there is one, or add one. Use the same(title — URL — accessed date)format as create mode.
- Preserve all required frontmatter fields from the existing note (
- Write the note. Call
mcp__dossier-mcp__update_notewith the updated content. Passslug,content, and all preserved frontmatter fields (title,date,updated,tags,related, plus any recipe-specific fields likestatus) per the tool's required parameters. - Backlink any new related slugs. For each slug newly added to
related(not previously present), callmcp__dossier-mcp__update_noteon that target note to add this note's slug to itsrelatedfield. Skip already-linked targets. - Surface what changed. Briefly state the slug and a section-level summary of changes — e.g., "added 2 new unknowns, integrated 3 answers into the Context section, added a Risks section." Avoid byte counts; describe the meaningful changes. The user can redirect or revise post-hoc.
- Return: the slug.
Style guidance
- Density over readability — pack in conclusions and reasoning, not just facts.
- Self-contained — key context inline, not only via links.
- Lead with the conclusion if there is one.
Future scope
- Stricter frontmatter validation
- Multi-note splitting for large captures
- Dedup against existing notes before writing
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.

