Second Brain Graph
Analyse the vault's link graph and report on its shape: orphan rate, average degree...
Install
npx skills add undefined-ui/second-brain-os --skill second-brain-graph -g -a claude-code -y- Repository
- undefined-ui/second-brain-os1.2k
- Category
- Engineering
- Updated
- 22d ago
- License
- MIT
- Context cost
- Lightabout 402 tokens
- Runs scripts
- No, instructions only
What it does
Analyse the vault's link graph and report on its shape: orphan rate, average degree, components, hubs, bridges and clusters, with what each number means for retrieval. Use this skill when the user asks about the health or structure of their graph, wants metrics, asks which pages are most connected or most isolated, or asks whether the vault is fragmented. Do NOT use for fixing what it finds, which is second-brain-lint, or for answering a content question.
Analyse the graph
The graph is the search space every answer is drawn from. Its shape decides whether retrieval reaches the relevant material in a few hops or reaches nothing.
Core rule
Report shape and what it means, never fix anything. This skill is read-only.
Workflow
- Run the scripts rather than reading files:
scripts/vault_stats.pyfor counts and degree,scripts/link_check.pyfor orphans and breaks,scripts/graph_export.pywhen deeper analysis is wanted. - Compute the four metrics: orphan rate, average degree, component count, stale-page rate.
- Identify hubs (pages that have swallowed the graph) and bridges (pages connecting otherwise separate clusters).
- Name the clusters. These are what the vault is actually about, which is reliably different from what the user would say it is about.
- Say what each number means for answering questions, not just the value.
Output format
Pages <n> | links <n> | avg degree <n>
Orphan rate <n>% (healthy under 5)
Components <n> (main holds <n>%)
Stale concepts <n>% (untouched 90+ days)
Hubs: <pages with outsized degree, and whether to split them>
Bridges: <pages connecting clusters, and what breaks if they are wrong>
Clusters: <what the vault is actually about>
What this means: <two or three sentences>
Calibration
Never report page count or word count as a health signal. Both rise whether the vault is improving or not.
A single reading says little. If the user has recorded previous numbers, compare against them; if not, suggest recording these.
