Menu
Analyze the knowledge graph for insights. Use when asked to "analyze connections", "graph report", "show hubs", "find orphans", or "knowledge map".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Must read guide on creating/editing mermaid charts with validation tools and syntax reference for all diagram types
Generate interactive HTML walkthroughs with clickable Mermaid diagrams (flowcharts and ER diagrams) that explain codebase features, flows, architecture, and database schemas. Use when asked to "walkthrough", "explain this flow", "how does X work", "trace the code path", "annotated diagram", "code walkthrough", "explain the architecture of", "walk me through", "database schema", "explain the tables", "data model".
Create a note from any resource: URL, book, podcast, article, video, GitHub repo, Reddit thread, PDF, quote, or raw idea. Trigger on "add", "save", "capture", "note this", "take notes on", or any request to record content in the knowledge base.
Add tweets to the Second Brain. Use when the user provides a Twitter/X URL and pasted tweet content, asking to "add a tweet", "save this tweet", or "capture this tweet".
Query your Second Brain with keyword search. Use when asked to "ask my notes", "what do I know about", "query my knowledge", "/ask", or when the user has a question that their notes might answer.
Create Obsidian templates for the Second Brain vault. Use when asked to "create a template", "make a template for", "add an Obsidian template", or "template for X".
| name | exploring-graph |
| description | Analyze the knowledge graph for insights. Use when asked to "analyze connections", "graph report", "show hubs", "find orphans", or "knowledge map". |
| allowed-tools | Read, Glob, Grep |
This skill analyzes the structure of connections in the knowledge base to surface insights.
Parse all wiki-links from every content file:
# Extract all wiki-links
grep -oh '\[\[[^]]*\]\]' content/*.md
# Get links per file
for f in content/*.md; do
echo "=== $f ==="
grep -o '\[\[[^]]*\]\]' "$f"
done
Build an adjacency list:
note-a → links to: [note-b, note-c]note-b → links to: [note-a]For each note, determine:
| Metric | Description |
|---|---|
| Outgoing links | Wiki-links in this note |
| Incoming links | Other notes linking to this one |
| Total connections | Outgoing + Incoming |
Notes with the highest total connections - these are central to the knowledge base.
Groups of notes that link heavily to each other but less to the rest. Identify by:
type: map note form visual clustersMap notes (type: map) act as cluster centers on the graph:
To find existing maps:
grep -l "type: map" content/*.md
Wiki-links pointing to non-existent notes.
## Knowledge Graph Analysis
### Overview
- Total notes: 15
- Total connections: 42
- Average connections per note: 2.8
### Hub Notes (Top 5 Most Connected)
| Note | Outgoing | Incoming | Total |
| ------------------- | -------- | -------- | ----- |
| [[central-concept]] | 5 | 8 | 13 |
| [[key-framework]] | 4 | 6 | 10 |
| ... | | | |
### Orphan Notes (Need Attention)
**Full Orphans** (isolated):
- `lonely-note.md` - no connections at all
**Dead Ends** (no incoming links):
- `new-note.md` - links out but not referenced
**Sources** (no outgoing links):
- `reference-only.md` - referenced but doesn't link
### Potential Clusters
**Vue Ecosystem** (5 notes, 12 internal links):
- [[vue-composables]]
- [[vue-testing]]
- [[nuxt-patterns]]
- ...
**AI/Agents** (3 notes, 6 internal links):
- [[12-factor-agents]]
- [[context-efficient-backpressure]]
- ...
### Connection Opportunities
Based on shared tags and titles, these notes might benefit from links:
- [[note-a]] and [[note-b]] share 3 tags but aren't linked
| Indicator | Healthy | Warning |
|---|---|---|
| Orphan rate | <10% | >20% |
| Avg connections | >2 | <1 |
| Broken links | 0 | Any |
When analyzing: