obsidian

Run a vault audit — eight metrics across frontmatter, tags, links, orphans, stale notes, folder discipline, with a prioritized fix plan

Bootstrap a new Obsidian vault — folders, filename conventions, frontmatter schema, tag taxonomy, templates, starter MOCs, home note, documentation notes

Clean up tags end-to-end — verify taxonomy, audit, plan, execute migrations in waves, verify, document

Run a full vault health sweep — audit, then sequentially fix broken links, frontmatter, tags, orphans, stale notes, then re-audit

Agents that act on an Obsidian vault. **Empty in v0.1.0** — placeholder for v0.3.

Vault organization expert — the senior practitioner who knows when to use each skill in the obsidian plugin and how to sequence them across multi-step workflows. Use this agent when a task spans multiple skills (audit + cleanup + restructure), requires sequencing, or needs senior-level judgment about which specialty skill applies for a given problem. Routes single-concern requests to the right specialty skill; orchestrates multi-step workflows by sequencing skill calls; defers to specialty skills for actual work — doesn't replace them. Tagline: Obsidian vault organization — opinionated structure, durable conventions, periodic hygiene.

Filename and note-title convention designer for Obsidian vaults. Helps you decide casing, hyphenation, claim-as-title vs topic-as-title, when to use IDs or dates in filenames, how to handle collisions, and how to use aliases instead of duplicate notes. Use this skill when establishing naming conventions for a new vault, when filenames are inconsistent, or when designing templates that auto-name new notes. Filenames in Obsidian double as note titles and as link targets, so this is structurally consequential.

Folder structure designer for Obsidian vaults. Helps you decide your top-level folders, how shallow or deep to go, and whether to organize by note type, by life area (PARA), by Johnny Decimal, or stay flat. Use this skill when starting a new vault, when your folder tree has grown past three levels, when you're deciding whether to add a new folder, or when migrating from a topic-based folder structure to a type-based one with MOCs handling topic. Pairs tightly with obsidian-moc-architect — folders for *where notes live*, MOCs for *what notes are about*.

Frontmatter (Properties) schema designer for Obsidian vaults. Helps you define what properties each note type should have, what their data types should be, which are required vs. optional, and how to keep schemas from drifting as the vault grows. Use this skill when you're introducing properties for the first time, when your frontmatter has gone freelance and every note has different keys, when you're about to add a new property and want it to fit, or when designing templates that enforce a schema.

Map of Content (MOC) architect for Obsidian vaults. Helps you decide when a topic earns a MOC, how to structure one, when to split or retire it, and how MOCs relate to the home note and to each other. Use this skill when a tag or folder is starting to feel like it should be a MOC, when an existing MOC is sprawling, when starting a vault and deciding how MOCs will carry the topical organization, or when migrating from a topic-folder structure to a MOC-driven one. Pairs with obsidian-folder-architect — folders for note location, MOCs for topic.

Entry-point router and map for the Obsidian plugin. Use this skill any time the user mentions Obsidian, "my vault," tag cleanup, frontmatter, MOCs, folder structure, vault audit, note types, links, or any other vault-organization concern. It gives Claude a 30-second map of the catalog, the opinionated stance, and which specialty skill or orchestrator to reach for next based on user intent. This skill does NOT do the work itself — it routes to the right specialty skill or orchestrator. Always loaded first when starting Obsidian-related work.