Skip to content
Skills Library
Personal productivity · Analysis

second-brain-graph

/second-brain-graph

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.

Licence
MIT
Last repository change
13.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Core rule
  2. Workflow
  3. Output format
  4. Calibration
Original SKILL.md headings · 46 lines, 248 words
SKILL.md preview
---
name: second-brain-graph
description: >-
  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

1. **Run the scripts** rather than reading files: `scripts/vault_stats.py` for
   counts and degree, `scripts/link_check.py` for orphans and breaks,
   `scripts/graph_export.py` when deeper analysis is wanted.
2. **Compute the four metrics:** orphan rate, average degree, component count,
   stale-page rate.
3. **Identify hubs** (pages that have swallowed the graph) and **bridges**
   (pages connecting otherwise separate clusters).
4. **Name the clusters.** These are what the vault is actually about, which is
   reliably different from what the user would say it is about.
5. **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.

Versions

The database has no other skills named second-brain-graph.

Database snapshot: 13.11.2026 · package version c55f091bb99f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100second-brain-query
    Answer a question from a second-brain vault by reading its own pages, citing the pages used, and saying plainly when the vault does not contain the answer. Use this skill whenever the user asks what they know about a topic, what they have read on something, what connects two…
  • 100second-brain-metrics
    Record 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…
  • 1003d-brain
    Use when someone asks to build a 3D brain, visualize their AIOS or second brain, turn their knowledge into an interactive graph, or run /3d-brain or /3D brain.
  • 100second-brain
    Use when the user wants to capture something into their second brain or personal notes vault ("remember that…", "add this idea", "log this", "note to self", "journal"), asks a question their own context would answer ("what are my goals", "what did I decide about X", "what's the…
  • 90vault-system
    Use when maintaining the vault ITSELF as a system, not its content: knowledge-graph build/rebuild/query (graphify), second-brain mapping, vault diagnose/audit/hygiene, drift detection, extract rules from vault, backfill journals, setup vault types, consolidate memory (index over…
  • 100personal-knowledge-vault
    Build and run a personal database ("second brain") as an Obsidian vault that an AI agent keeps linked and tidy - wings separated by audience (public, private, strict), Maps of Content, a frontmatter contract, a no-orphan link rule, graph colours, Bases dashboards for vault…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.