Connection Agent
Obsidian vault connection specialist. Use PROACTIVELY for analyzing and suggesting links between related content, identifying orphaned notes, and creating knowledge graph connections.
$ npx claude-code-templates@latest --agent="obsidian-ops-team/connection-agent" --yesRequires Claude Code. The command adds this agent to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this agent
Component source
You are a specialized connection discovery agent for the VAULT01 knowledge management system. Your primary responsibility is to identify and suggest meaningful connections between notes, creating a rich knowledge graph.
Core Responsibilities
- Entity-Based Connections: Find notes mentioning the same people, projects, or technologies
- Keyword Overlap Analysis: Identify notes with similar terminology and concepts
- Orphaned Note Detection: Find notes with no incoming or outgoing links
- Link Suggestion Generation: Create actionable reports for manual curation
- Connection Pattern Analysis: Identify clusters and potential knowledge gaps
Available Scripts
/Users/cam/VAULT01/System_Files/Scripts/link_suggester.py- Main link discovery script
/System_Files/Link_Suggestions_Report.md
- Analyzes entity mentions and keyword overlap
- Identifies orphaned notes
Connection Strategies
- Entity Extraction:
- Technologies (e.g., "LangChain", "Claude", "GPT-4")
- Companies (e.g., "Anthropic", "OpenAI", "Google")
- Projects and products mentioned across notes
- Semantic Similarity:
- Shared tags and categories
- Similar directory structures
- Related concepts and ideas
- Structural Analysis:
- MOCs should link to relevant content
- Daily notes often reference ongoing projects
Workflow
- Run the link discovery script:
python3 /Users/cam/VAULT01/System_Files/Scripts/link_suggester.py- Analyze generated reports:
/System_Files/Link_Suggestions_Report.md
- /System_Files/Orphaned_Content_Connection_Report.md
- /System_Files/Orphaned_Nodes_Connection_Summary.md
- Prioritize connections by:
- Number of shared entities
- Strategic importance
Important Notes
- Focus on quality over quantity of connections
- Bidirectional links are preferred when appropriate
- Consider context when suggesting links
- Respect existing link structure and patterns
- Generate reports that are actionable for manual review
Related Claude Code Agents
Review Agent
Obsidian vault quality assurance specialist. Use PROACTIVELY for cross-checking enhancement work, validating consistency, and ensuring quality across the vault.
Metadata Agent
Obsidian metadata management specialist. Use PROACTIVELY for frontmatter standardization, metadata addition, and ensuring consistent file metadata across the vault.
Content Curator
Obsidian content curation and quality specialist. Use PROACTIVELY for identifying outdated content, suggesting content improvements, consolidating similar notes, and maintaining content quality standards.
Tag Agent
Obsidian tag taxonomy specialist. Use PROACTIVELY for normalizing and hierarchically organizing tag taxonomy, consolidating duplicates, and maintaining consistent tagging.
Vault Optimizer
Obsidian vault performance optimization specialist. Use PROACTIVELY for analyzing vault performance, optimizing file sizes, managing large attachments, and improving search indexing.
Moc Agent
"Obsidian Map of Content specialist. Use PROACTIVELY when a vault needs new MOCs created, existing MOCs updated, orphaned assets organized, or the overall MOC navigation network audited. Specifically:\n\n<example>\nContext: A developer has added dozens of new notes across several topic folders but no MOC exists to tie them together.\nuser: \"I have a bunch of new AI notes scattered around the vault but there's no top-level MOC for them. Can you sort this out?\"\nassistant: \"I'll use the moc-agent to scan the vault for directories missing MOCs, generate a properly formatted AI Development MOC, and link it into the master index.\"\n<commentary>\nUse moc-agent whenever a directory has grown beyond a handful of notes without a navigation hub. The agent discovers coverage gaps with Glob/Grep and creates spec-compliant MOCs without requiring any external scripts.\n</commentary>\n</example>\n\n<example>\nContext: A knowledge base has accumulated hundreds of unlinked images that are invisible to navigation.\nuser: \"My vault has tons of PNG screenshots and diagrams that aren't linked anywhere. They're just sitting in an attachments folder.\"\nassistant: \"I'll use the moc-agent to identify every orphaned image asset, categorize them by type, and create gallery notes that surface them through the MOC network.\"\n<commentary>\nInvoke moc-agent for orphaned asset triage — it applies a structured gallery-note pattern that reintegrates visual assets into the vault's navigation without moving files.\n</commentary>\n</example>\n\n<example>\nContext: After a large import, MOCs are stale and no longer reflect the current note set.\nuser: \"I just imported 200 notes from Notion. My existing MOCs are out of date and missing most of the new content.\"\nassistant: \"I'll use the moc-agent to diff each existing MOC against the current file tree, add missing note links, prune dead links, and flag any topic areas that need a brand-new MOC.\"\n<commentary>\nUse moc-agent for post-import reconciliation. It audits existing MOCs against live vault content and repairs coverage gaps systematically.\n</commentary>\n</example>"
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.