capture
SolidQuick note capture with automatic wikilink suggestions to related existing notes. Use when the user wants to save a single, specific, titled idea, insight, or piece of information to the vault. Do NOT use for: unstructured multi-thread thought dumps (use braindump), saving a URL for later (use bookmark), deeply summarizing an article or URL (use summarize), processing a book (use reading-notes), or teaching the agent a preference (use learn).
Install
Quality Score: 81/100
Skill Content
Details
- Author
- onebrain-ai
- Repository
- onebrain-ai/onebrain
- Created
- 4 months ago
- Last Updated
- 5 days ago
- Language
- Shell
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
vault-note-capture
When user says "take a note", "note this down", "write it down", "save this", "remember this", "make a note of this" (or paraphrase), write a markdown note to ~/Vault/Notes/<Category>/. Invoke this skill on those phrases.
create-obsidian-note
Capture notes into the user's personal Obsidian vault the way its conventions require, and work with its Bases and Categories. Use this WHENEVER the user wants to save, capture, or jot down a note, insight, concept, or learning into their Obsidian vault, or create or edit a Base or Category there, even if they never say "Obsidian", as long as the intent is clearly to persist something into their personal notes. Use it too when they ask where a note should go or how the vault is organized.
kg-capture
Knowledge capture rules. Capture mid-conversation, not after — context is cached, so a write costs almost nothing now but saves full re-derivation next session. Good moments to capture (as things happen, not at task end): - Opened files with no component node → a brief node now saves a re-read later - Discovered how two things connect → an edge, while the insight is fresh - Understood why something works a certain way → a note on the existing node - 10+ min debugging resolved → root cause node before moving on - User expressed a preference, style, or constraint → user-level node - User corrected your approach → capture what was missed, not just the fix - Explained something non-obvious → node before it scrolls away - Approach agreed with user → capture the methodology, not just the decision - Architectural decision made → node with rationale in notes - Context window feels deep → a good moment to check for anything unrecorded When reading a file with no component node, consider creating one. Gist = what it ha