>- 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.
npx skills add https://github.com/undefined-ui/second-brain-os --skill second-brain-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.
Scope against the vault first. Most of the work in a good report is knowing what
you do not need to look up.
missing entirely. That answer is the research plan.
more first.
a URL behind it.
conclusion.
output/ and offer to ingest it back as a source.## Question
## What the vault covers (with [[page]] citations)
## Where sources disagree
## What I could not establish
## What would change this
## Pages read: <list>
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.
Take undefined-ui/second-brain-report 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.