undefined-ui/second-brain-os / skills/second-brain-review
second-brain-review
VerifiedProduce a periodic review of a second-brain vault: what was added, which topics are growing, what contradicts what, which questions are still open, and what is worth reading next. Use this skill whenever the user asks for a weekly or monthly review, asks what changed in their vault, what they have been learning about lately, or what they should look at next, and when a scheduled review task fires. Do NOT use for structural linting, for ingesting sources, or for answering a specific factual question.
Review the vault
Capture systems fail at the point where nothing comes back out. A review is the loop that closes: it turns a week of ingestion into something the owner reads and acts on, and it is what makes the vault feel alive rather than archival.
Core rule
A review reports on the vault, not on the agent's activity. Nobody needs to know how many tool calls ran; they need to know what they now know.
Workflow
- Diff the period. New and updated pages since the last review, from
log.mdand frontmatter dates. - Find the clusters. Which concepts gained the most links. That is where the owner's attention actually went, which is often not where they think it went.
- Surface contradictions recorded during the period and still unresolved.
- List open questions from concept and synthesis pages.
- Find the neglected. Pages linked often but thin, or gaps in
index.mdthat keep getting referenced. - Recommend three things to read or write next, each tied to a specific page.
Output format
## Week of <date>
Added: <n> pages, <n> sources ingested
### Where your attention went
<two or three sentences on the clusters>
### Unresolved
<contradictions and open questions, each linked>
### Thin spots
<pages that are referenced more than they deserve given their content>
### Next
1. <specific action tied to a page>
2.
3.
Calibration
Reviews that list everything get skimmed and then ignored. Keep it under a page. Three recommendations, not ten. If a week produced nothing worth reporting, say that in one line instead of manufacturing insight.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |