agentleFS
AbilityaiAbilityai/cornelius/.claude/skills/analyze-kb/SKILL.md

analyze-kb

Skill109 starsChanged 39 days agoMITView on GitHub

Analyze knowledge base structure and update the knowledge-base-analysis.md report

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Local Brain Search for all semantic search operations.

    line 12
  2. Very specific:

    Use Glob to explore directory structure:

    line 44
  3. Very specific:

    Read key hub notes from major clusters using Read tool (Dopamine, Self/Buddhism, Decision-Making, Flow, etc.)

    line 50
  4. Distinctive:

    Use Local Brain Search to identify hub notes and bridges:

    line 52
  5. Very specific:

    Use Edit or Write to update the knowledge-base-analysis.md file with a condensed report (target: ~600-800 lines max):

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Analyze the Obsidian knowledge base structure and regenerate a condensed, manageable analysis report.

Local Brain Search

Use Local Brain Search for all semantic search operations.

Scripts:

# Semantic search
resources/local-brain-search/run_search.sh "query" --limit 10 --json

# Find connections
resources/local-brain-search/run_connections.sh "Note Name" --json

# Get graph statistics
resources/local-brain-search/run_connections.sh --stats --json

# Find hub notes
resources/local-brain-search/run_connections.sh --hubs --json

# Find bridge notes
resources/local-brain-search/run_connections.sh --bridges --json

Follow these steps:

  1. Get vault statistics using Local Brain Search:
    resources/local-brain-search/run_connections.sh --stats --json
  2. List all notes with full directory tree using Bash find:
    find $VAULT_BASE_PATH/Brain -name "*.md" -type f | head -50
  3. Use Glob to explore directory structure:
    • All notes: Brain/**/*.md
    • Permanent notes: Brain/02-Permanent/*.md
    • MOCs: Brain/03-MOCs/*.md
    • Sources: Brain/01-Sources/**/*.md
  4. Read key hub notes from major clusters using Read tool (Dopamine, Self/Buddhism, Decision-Making, Flow, etc.)
  5. Use Local Brain Search to identify hub notes and bridges:

    resources/local-brain-search/run_connections.sh --hubs --json
    resources/local-brain-search/run_connections.sh --bridges --json

    Fingerprint scope note: --hubs/--bridges are the cognitive-fingerprint axis. Scope enforcement is now ON (MEMORY_CONFIG['scope']['enforce']=True, since 2026-06-25; see SCOPE-IMPLEMENTATION-PLAN.md), so they compute on the core subgraph only (02-Permanent, 03-MOCs, AI Extracted Notes, 01-Sources). Document-Insights-inflated hubs (Dopamine/Flow) no longer appear; the true core hubs (MOC - Eight-Circuit, Decision Making, Gilbert, Tetlock, Hagen) surface. --stats stays whole-graph (it answers "how big is the store", not "who am I"). Note which mode is active when recording hubs.

  6. Pull BDG statistics for layer distribution and lifecycle phases:
    resources/brain-graph/run_brain_graph.sh status --json
  7. Analyze thematic clusters, hierarchical organization, and conceptual architecture
  8. Use Edit or Write to update the knowledge-base-analysis.md file with a condensed report (target: ~600-800 lines max):
    • Executive summary with key statistics
    • Hierarchical structure mapping (condensed)
    • 6 major thematic hubs with hub nodes (core thesis + key notes only)
    • Network properties and connectivity (metrics + critical bridges)
    • Content topology and source analysis (top-tier influences only)
    • Intellectual trajectory and maturity assessment (phases + current focus)
    • Recommendations for enhancement (high priority only)

CRITICAL OUTPUT REQUIREMENTS:

  • Length target: 600-800 lines maximum (50% of previous verbose reports)
  • Prioritize: Core insights, actionable frameworks, critical statistics, key bridge notes
  • Eliminate: Excessive examples, redundant explanations, verbose elaborations
  • Focus: What's unique, what's actionable, what's growing, what's next
  • Style: Bullet points over paragraphs, tables over lists where appropriate
  • No duplication: Say things once, clearly, then move on

Generate a condensed, scannable, high-signal report that reveals the knowledge base's personality, cognitive fingerprint, and growth opportunities without overwhelming detail.

State Dependencies

SourceLocationReadWriteDescription
Brain notesBrain/**/*.mdXAll vault notes for analysis
Permanent notesBrain/02-Permanent/XCore insights
MOCsBrain/03-MOCs/XMap of Content hubs
SourcesBrain/01-Sources/XReference materials
AI InsightsBrain/AI Extracted Notes/XAI-extracted notes
Document InsightsBrain/Document Insights/XResearch session notes
Book scopesBrain/Books/XPer-book scopes (non-core, family)
ChangelogsBrain/05-Meta/Changelogs/XSession logs
Local Brain Searchresources/local-brain-search/XGraph statistics, hubs, bridges
Knowledge base analysisknowledge-base-analysis.mdXXOutput report

Completion Checklist

  • Vault statistics retrieved from Local Brain Search
  • Directory structure explored with Glob
  • Key hub notes read (Dopamine, Buddhism, Decision-Making, Flow, AI)
  • Hub notes and bridges identified
  • Thematic clusters analyzed
  • knowledge-base-analysis.md updated with condensed report
  • Report is 600-800 lines (not verbose)
  • Executive summary includes key statistics
  • 6 major thematic hubs documented
  • Network properties and bridges noted
  • Recommendations provided (high priority only)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.