Individual skill
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.
skills/second-brain-report/SKILL.md
Source commit 53aea8231aff3024352e21839dc08668f7ecc0b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,518
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- knowledge-graph Repository topic
- knowledge-management Repository topic
- llm Repository topic
- mcp Repository topic
- obsidian Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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.