Claude Skill

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

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download undefined-ui-second-brain-os-skills_second-brain-graph-347feee.zip · 1 KB
Part of undefined-ui/second-brain-os — 18 skills

Install

skills CLI npx skills add https://github.com/undefined-ui/second-brain-os/tree/main/skills/second-brain-graph
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install undefined-ui-second-brain-os@llmmart
Git git clone https://github.com/undefined-ui/second-brain-os.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole undefined-ui/second-brain-os collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Files (second-brain-os)
  • SKILL.md 2.1 KB
    ---
    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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related