capture

Capture

Write a note into the vault from a source the user hands you. One arc, six steps: open (search, fetch, ask why) -> read the primary source -> create through sb -> leave it in the inbox -> link connections -> fold in follow-ups. "Read this and make a note" means all six; the connect step won't happen unless this skill runs it.

Note shape: references/note-format.md. sb commands: ../obsidian/references/sb-cli.md.

Step 0: Locate the vault

npx @techpickles/sb vault info
npx @techpickles/sb config qmd-collection

Read the vault's own CLAUDE.md if you haven't this session. Its policy (destinations, status vocabulary, disambiguation) overrides the defaults here.

Step 1: Open - search, start the fetch, ask why

Do these in order, then end the turn. Nothing is written yet.

1. Start reading the source in the background (Bash with run_in_background), using the first rung of references/fetch-ladder.md. Step 2 collects the result.

2. Search the vault while it runs, through the qmd MCP tools (shelling out to qmd hits Metal-init failures under the sandbox):

   mcp__qmd__query
     searches: [{type: 'lex', query: '<one distinctive term>'},
                {type: 'lex', query: '<another term>'},
                {type: 'vec', query: '<what the note would say>'}]
     collection: <from sb config qmd-collection>
     intent: '<why you are searching>'
     rerank: false
   

   Each lex is one or two terms, because lex ANDs its terms. Also Glob today's inbox captures (*/11 Inbox*/<YYYYMMDD>*.md), since the qmd index lags same-day notes.

3. Send one message with: the hits (path + snippet + why each looks strong or weak; qmd scores are only ranks), the question "what made you grab this?", and on a strong match "extend or start a new one?".

4. End the turn.

Then, keyed to what you observe:

• The request already states a reason: skip the why question and carry on.
• The fetch has failed when you send the message: say so there, in one line, and ask the same questions. The why question and the hits don't wait on the fetch.
• The fetch finishes before a reply: write with **Why I saved this:** TODO.
• A strong-match question is open: wait for the reply, then write.
• qmd tools aren't loaded yet: use Grep, say it was keyword-only, and run qmd before writing.
• A qmd path starts with second-brain/: strip that prefix to get the path on disk.
• The thing's name is unfamiliar: let the fetch land before the vec query.
• A search misses, or the user says "that isn't the one": references/search-recovery.md.