Second Brain Query Agent 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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/NicholasSpisak/second-brain --skill second-brain-queryThe instruction itself
12 sections, as written by the authorSecond 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:
- Create a new page in
wiki/synthesis/with proper frontmatter - Add an entry to
wiki/index.mdunder Synthesis - 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
Other skills for the same job
different authors, same section of the catalogue
Master receipt scanning operations including parsing, debugging, enhancing accuracy, and database integration. Use when working with receipts, images, OCR issues, expense categorization, or troubleshooting receipt uploads.
This skill helps you work with the receipt scanning tools in the nonprofit_finance_db project. It includes manual entry tools, automated OCR scanning, and database integration for tracking receipts...
Answer an explicitly vault-scoped question from an Obsidian wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the wiki. Do not route ordinary general-knowledge questions here.
Use CloudBase document database WeChat MiniProgram SDK to query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries.
Use CloudBase document database WeChat MiniProgram SDK to query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries.
Natural-language time tracking: parse what the user says they did into Activity/Minutes/Date rows in their own Notion database — asking instead of guessing when unsure.
Retrieve records from NCBI databases using Biopython Bio.Entrez (EFetch, ESummary). Use when downloading sequences, fetching GenBank/GenPept records, getting document summaries, parsing nested XML, navigating GI deprecation, choosing between rettype+retmode combinations, and parsing into Biopython SeqRecord/SwissProt objects. Covers nucleotide, protein, gene, pubmed, sra, gds, taxonomy, snp, clinvar.
> Query DailyMed for FDA drug label / package insert information. Use whenever the user asks about drug labeling, SPL documents, prescribing information, NDC codes, or needs to look up current FDA-approved drug details by name or NDC. Supports single entity or batch queries.
How to use it
Take nicholasspisak/second-brain-query from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.