Architect Moc Agent

Automated Map of Content generator that builds, maintains, and interconnects navigational hub notes across Obsidian vault directories.

When to Use This Agent

Choose this agent when you need to:

• Generate Maps of Content for directories that lack navigational hub notes
• Rebuild or update existing MOCs to reflect recently added content
• Organize orphaned images and visual assets into categorized gallery notes
• Create a hierarchical MOC network linking parent topics to subtopic hubs

Consider alternatives when:

• You need to fix tag inconsistencies across the vault (use Tag Agent Partner)
• Your focus is on content quality and deduplication rather than navigation structure

Quick Start

Configuration

Copy
name: architect-moc-agent
type: agent
category: obsidian-ops-team

Example Invocation

Copy
claude agent:invoke architect-moc-agent "Generate MOCs for all directories missing navigation hubs"

Example Output

=== MOC Generation Report ===
Vault: ~/KnowledgeBase (87 directories scanned)

DIRECTORIES WITHOUT MOCs: 12 found
  - AI/Agents/ → Generated: MOC - AI Agents.md (14 linked notes)
  - Projects/Backend/ → Generated: MOC - Backend Projects.md (9 linked notes)
  - Research/Papers/ → Generated: MOC - Research Papers.md (23 linked notes)

ORPHANED IMAGES: 31 organized
  - 18 screenshots → Gallery - Screenshots.md
  - 8 diagrams → Gallery - Architecture Diagrams.md
  - 5 logos → Gallery - Brand Assets.md

MASTER INDEX: Updated with 12 new MOC entries

Core Concepts

MOC Hierarchy Levels Overview

Aspect	Details
Master Index	Top-level MOC linking to all domain-specific MOCs
Domain MOCs	Mid-level hubs covering broad knowledge areas like AI or DevOps
Topic MOCs	Focused hubs for specific topics within a domain
Gallery Notes	Specialized MOCs organizing visual assets by category

MOC Network Architecture

┌─────────────┐     ┌─────────────┐
│  Directory   │────▶│  MOC        │
│  Scanner     │     │  Generator  │
└─────────────┘     └─────────────┘
        │                   │
        ▼                   ▼
┌─────────────┐     ┌─────────────┐
│  Orphaned    │────▶│  Master     │
│  Asset Org   │     │  Index Sync │
└─────────────┘     └─────────────┘

Configuration

Parameter	Type	Default	Description
moc_directory	string	"/map-of-content/"	Root directory where generated MOC files are stored
naming_pattern	string	"MOC - {topic}.md"	Naming convention for generated Map of Content files
min_notes_for_moc	integer	3	Minimum notes in a directory before a MOC is generated
include_galleries	boolean	true	Whether to generate gallery notes for orphaned images
frontmatter_type	string	"moc"	Value assigned to the type field in MOC frontmatter

Best Practices

1. Keep MOCs as Navigation, Not Content A Map of Content should contain links, brief descriptions, and organizational structure. Avoid putting substantive content directly in MOCs; instead link to the notes where that content lives. This prevents duplication and keeps MOCs lightweight.

2. Set a Minimum Note Threshold Generating a MOC for a directory with only one or two notes adds unnecessary overhead. Configure min_notes_for_moc to at least 3 so that MOCs are only created where they provide genuine navigational value.

3. Use Bidirectional Links Between MOC Layers Every topic MOC should link up to its parent domain MOC, and the domain MOC should link down to its child topics. This two-way linking ensures navigation works regardless of where a user enters the vault.

4. Review Gallery Notes for Misclassification Automated image categorization relies on filename patterns and directory context. After generation, review gallery notes to ensure screenshots are not mixed with diagrams and that the assigned categories match the actual content.

5. Schedule Regular MOC Refresh Cycles As new notes are added, MOCs become stale. Run the agent monthly or after major content additions to ensure all MOCs accurately reflect the current vault contents and new notes are properly linked.

Common Issues

1. MOC generated for a directory that already has a manually created index The agent checks for files matching the naming_pattern but does not detect custom index notes with different names. Add an is_moc: true frontmatter field to your existing index notes so the scanner recognizes them.

2. Orphaned images not detected in nested subdirectories By default the scanner checks immediate directory children only. Enable recursive scanning by setting recursive_asset_scan: true in the configuration to capture images buried in deeper folder structures.

3. Master Index becomes unwieldy with too many MOC entries Group MOC entries in the Master Index by domain using heading sections rather than a flat list. The agent supports group_by_domain: true which organizes entries under their top-level directory headings.