/second-brain-query
Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki.
$ npx -y skills add NicholasSpisak/second-brain --skill second-brain-query --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/second-brain-query
Context preview
The summary Claude sees to decide when to auto-load this skill.
Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki.
SKILL.md
second-brain-query.SKILL.mdname: second-brain-query
description: >
Answer questions against the knowledge base wiki. Use when the user
asks a question about their collected knowledge, wants to explore
connections between topics, says "what do I know about X", or wants
to search their wiki.
allowed-tools: Bash Read Write Edit Glob Grep
Second Brain — Query
Answer questions by searching and synthesizing knowledge from the wiki.
Search Strategy
1. Start with the index
Read `wiki/index.md` to identify relevant pages. Scan all category sections (Sources, Entities, Concepts, Synthesis) for entries related to the question.
2. Use qmd for large wikis
If `qmd` is installed (check with `command -v qmd`), use it for search:
qmd search "query terms" --path wiki/
This is especially useful when the wiki has grown beyond ~100 pages where scanning the index becomes inefficient.
3. Read relevant pages
Read the wiki pages identified by the index or search. Follow `[[wikilinks]]` to pull in related context from linked pages. Read enough pages to give a thorough answer, but don't read the entire wiki.
4. Check raw sources if needed
If the wiki pages don't fully answer the question, check relevant source summaries in `wiki/sources/` for additional detail. Only go to files in `raw/` as a last resort.
Synthesize the Answer
Format
Match the answer format to the question:
- **Factual question** → direct answer with citations
- **Comparison** → table or structured comparison
- **Exploration** → narrative with linked concepts
- **List/catalog** → bulleted list with brief descriptions
Citations
Always cite wiki pages using `[[wikilink]]` syntax. Example:
> According to [[Source - Article Title]], the key finding was X. This connects to the broader pattern described in [[Concept Name]], which [[Entity Name]] has also explored.
Offer to save valuable answers
If the answer produces something worth keeping — a comparison, analysis, new connection, or synthesis — offer to save it:
> "This comparison might be useful to keep in your wiki. Want me to save it as a synthesis page?"
If the user agrees: 1. Create a new page in `wiki/synthesis/` with proper frontmatter 2. Add an entry to `wiki/index.md` under Synthesis 3. Append to `wiki/log.md`: `## [YYYY-MM-DD] query | Question summary`
Conventions
- **Search the wiki first.** Only go to raw sources if the wiki doesn't have the answer.
- **Cite your sources.** Every factual claim should link to the wiki page it came from.
- **Valuable answers compound.** Encourage saving good analyses back into the wiki.
- Use `[[wikilinks]]` for all internal references. Never use raw file paths.
Related Skills
- `/second-brain-ingest` — process new sources into wiki pages
- `/second-brain-lint` — health-check the wiki for issues
Read more
name: second-brain-query description: > Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki. allowed-tools: Bash Read Write Edit Glob Grep
Second Brain — Query
Answer questions by searching and synthesizing knowledge from the wiki.
Search Strategy
1. Start with the index
Read `wiki/index.md` to identify relevant pages. Scan all category sections (Sources, Entities, Concepts, Synthesis) for entries related to the question.
2. Use qmd for large wikis
If `qmd` is installed (check with `command -v qmd`), use it for search:
qmd search "query terms" --path wiki/
This is especially useful when the wiki has grown beyond ~100 pages where scanning the index becomes inefficient.
3. Read relevant pages
Read the wiki pages identified by the index or search. Follow `[[wikilinks]]` to pull in related context from linked pages. Read enough pages to give a thorough answer, but don't read the entire wiki.
4. Check raw sources if needed
If the wiki pages don't fully answer the question, check relevant source summaries in `wiki/sources/` for additional detail. Only go to files in `raw/` as a last resort.
Synthesize the Answer
Format
Match the answer format to the question:
- **Factual question** → direct answer with citations
- **Comparison** → table or structured comparison
- **Exploration** → narrative with linked concepts
- **List/catalog** → bulleted list with brief descriptions
Citations
Always cite wiki pages using `[[wikilink]]` syntax. Example:
> According to [[Source - Article Title]], the key finding was X. This connects to the broader pattern described in [[Concept Name]], which [[Entity Name]] has also explored.
Offer to save valuable answers
If the answer produces something worth keeping — a comparison, analysis, new connection, or synthesis — offer to save it:
> "This comparison might be useful to keep in your wiki. Want me to save it as a synthesis page?"
If the user agrees: 1. Create a new page in `wiki/synthesis/` with proper frontmatter 2. Add an entry to `wiki/index.md` under Synthesis 3. Append to `wiki/log.md`: `## [YYYY-MM-DD] query | Question summary`
Conventions
- **Search the wiki first.** Only go to raw sources if the wiki doesn't have the answer.
- **Cite your sources.** Every factual claim should link to the wiki page it came from.
- **Valuable answers compound.** Encourage saving good analyses back into the wiki.
- Use `[[wikilinks]]` for all internal references. Never use raw file paths.
Related Skills
- `/second-brain-ingest` — process new sources into wiki pages
- `/second-brain-lint` — health-check the wiki for issues
An LLM-maintained personal knowledge base built on the LLM Wiki pattern. Drop raw sources into a folder, let the LLM compile them into a structured wiki, and browse it all in Obsidian.
Repo: NicholasSpisak/second-brain
Other skills on second-brain.
- /second-brain-ingest
Process raw source documents into wiki pages. Use when the user adds files to raw/ and wants them ingested, says "process this source", "ingest this article", "I added something to raw/", or wants to incorporate new material into their knowledge base.
Open skill - /second-brain-lint
Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.
Open skill - /second-brain
Set up a new Obsidian knowledge base with the LLM Wiki pattern. Use when the user wants to create a second brain, initialize a vault, set up a personal knowledge base, or says "onboard". Guides through an interactive wizard to configure vault name, location, domain, agent
Open skill

