second-brain-report
/second-brain-report
Produce a research report from the vault: scope the question against existing pages, name the gaps, and write findings with citations, disagreements and limits. Use this skill when the user asks for a research report, a deep write-up on a topic, or wants to understand a subject thoroughly using what they have collected. Do NOT use for a quick answer from the vault, for drafting an article in the user's voice, or for summarising a single source.
- Author
- undefined-ui ↗
- Repository
- second-brain-os ↗
- Licence
- MIT
- Last repository change
- 13.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Produce a research report from the vault: scope the question against existing pages, name the gaps, and write findings with citations, disagreements and limits. Use this skill when the user asks for a research report, a deep write-up on a topic, or wants to understand a subject thoroughly using what they have collected. Do NOT use for a quick answer from the vault, for drafting an article in the user's voice, or for summarising a single source.
Original author description
Produce a research report from the vault: scope the question against existing pages, name the gaps, and write findings with citations, disagreements and limits. Use this skill when the user asks for a research report, a deep write-up on a topic, or wants to understand a subject thoroughly using what they have collected. Do NOT use for a quick answer from the vault, for drafting an article in the user's voice, or for summarising a single source.
How it works
- Core rule
- Workflow
- Output format
- Calibration
SKILL.md preview
--- name: second-brain-report description: >- Produce a research report from the vault: scope the question against existing pages, name the gaps, and write findings with citations, disagreements and limits. Use this skill when the user asks for a research report, a deep write-up on a topic, or wants to understand a subject thoroughly using what they have collected. Do NOT use for a quick answer from the vault, for drafting an article in the user's voice, or for summarising a single source. --- # Write a research report A report that presents only findings looks stronger and is less useful, because the reader cannot tell where it is load-bearing and where it is thin. ## Core rule Scope against the vault first. Most of the work in a good report is knowing what you do not need to look up. ## Workflow 1. **Inventory what exists.** Which pages cover this, what is thin, what is missing entirely. That answer is the research plan. 2. **Report the gaps before writing,** so the user can decide whether to ingest more first. 3. **Write from pages, citing pages.** Every claim traces to a source page with a URL behind it. 4. **Record disagreement** where sources conflict, with dates and who says what. 5. **State what could not be established** and what evidence would change the conclusion. 6. **Save to `output/`** and offer to ingest it back as a source. ## Output format ``` ## Question ## What the vault covers (with [[page]] citations) ## Where sources disagree ## What I could not establish ## What would change this ## Pages read: <list> ``` ## Calibration If the vault covers less than half the question, say so at the top rather than producing a report that reads as complete. Never fill a gap from general knowledge without labelling it as outside the vault. A report whose sources cannot be checked is worth less than a short one that can.
Versions
The database has no other skills named second-brain-report.
Database snapshot: 13.11.2026 · package version bf6a55dfe95b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100second-brain-query
Answer a question from a second-brain vault by reading its own pages, citing the pages used, and saying plainly when the vault does not contain the answer. Use this skill whenever the user asks what they know about a topic, what they have read on something, what connects two… - 100second-brain-ingest
Turn raw source material in a second-brain vault into linked wiki pages: read the source, split it into concepts and entities, write or update pages, connect them to existing pages, and record the run in the log. Use this skill whenever the user drops a file into raw/, pastes an… - 100second-brain
Use when the user wants to capture something into their second brain or personal notes vault ("remember that…", "add this idea", "log this", "note to self", "journal"), asks a question their own context would answer ("what are my goals", "what did I decide about X", "what's the… - 100second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault''s queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file… - 85obsidian-second-brain
Use an Obsidian vault as the agent's persistent second brain. Use when the user asks to set up their second brain, Obsidian memory or a notes vault, asks to save or recall project knowledge, or when starting/ending a work session and a vault is configured (a LAYOUT.md exists in… - 100second-brain
Operate as the user's personal "second brain" — a compile-not-retrieve knowledge base following Andrej Karpathy's LLM Wiki pattern. Use when the user wants to ingest/save an article, note, paper, or source into their knowledge base; answer a question from their accumulated wiki;…