undefined-ui/second-brain-os / skills/second-brain-metrics
second-brain-metrics
UnverifiedRecord a dated snapshot of the vault's health numbers and compare against previous snapshots so trends are visible. Use this skill for a monthly or quarterly check, when the user asks whether the vault is improving, or asks to track its numbers over time. Do NOT use for a one-off graph analysis, which is second-brain-graph, or for structural repairs.
Record metrics
A single reading tells you almost nothing. Direction over months is the information, and nobody remembers what last quarter's orphan rate was.
Core rule
Four numbers, appended to a dated log, compared against the last entry. Never page count or word count.
Workflow
- Run
scripts/vault_stats.pyandscripts/link_check.py. - Record: orphan rate, average degree, component count, stale-concept rate, with the date and total pages for context.
- Append to the metrics note. Never overwrite previous entries.
- Compare against the last snapshot and name what moved.
- Interpret only what changed. A stable number needs no commentary.
Output format
<date> | pages <n>
orphan rate <n>% (<+/-n> since <date>)
avg degree <n> (<+/-n>)
components <n> (main <n>%)
stale concepts <n>% (<+/-n>)
Moved: <what changed and the likely cause>
Watch: <the one number to fix, or none>
Calibration
A rising orphan rate with a rising page count means ingestion has stopped linking. That is the single most important pattern in this report and it should be called out explicitly, not left in the numbers.
Do not recommend more than one thing to fix. A metrics report with five action items gets ignored.
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: 463k | 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: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |