capturelisted

Use when the user asks to read a source and make a note for it, create or find an atomic note, or check whether a note already exists. Triggers on "read <url> and make a note", "make a note for", "create (or find) an atomic note", "do we have notes about X?", "check if we have a note for", "capture this", "put together a note", "distill this", and on a bare URL/PDF/tweet/thread handed over with intent to write it up. Covers the whole loop as one arc - search the vault first, read the primary source, write the note through the sb CLI, then offer connections. Use inside an Obsidian vault or anywhere a vault is configured. Do NOT use for draining an accumulated inbox backlog (that is process-inbox), for extracting insights from the current conversation (that is devlog), or for routing already-captured notes to their homes (that is route).
technicalpickles/pickled-claude-plugins · ★ 10 · Data & Documents · score 75

Install: claude install-skill technicalpickles/pickled-claude-plugins

# Capture Write a note into the vault from a source the user hands you. One arc, five steps: **search → read the primary source → create through sb → leave it in the inbox → offer connections.** This is the dominant vault interaction. Do not decompose it into separate asks; the user saying "read this and make a note" means all five steps, and the connect step in particular will not happen unless this skill runs it. See [references/note-format.md](references/note-format.md) for frontmatter and body shape. See [../obsidian/references/sb-cli.md](../obsidian/references/sb-cli.md) for the full sb command surface. ## Step 0: Locate the vault ```bash npx @techpickles/sb vault info npx @techpickles/sb config qmd-collection ``` Read the vault's own `CLAUDE.md` if you haven't this session. Vault-specific policy (destinations, status vocabulary, disambiguation rules) overrides the defaults here. ## Step 1: Search before creating - never skip this Run a `lex` + `vec` pair through the **qmd MCP tools**, not the shell. (`mcp__qmd__query` is the working path; shelling out to `qmd` hits Metal-init failures under the sandbox.) ``` mcp__qmd__query searches: [{type: 'lex', query: '<topic terms>'}, {type: 'vec', query: '<what the note would say>'}] collection: <from sb config qmd-collection> intent: '<why you are searching>' rerank: false # CPU-only box, reranking is not worth the latency here ``` Show the user what already exists - **path + score + snippet*