Help us improve
Share bugs, ideas, or general feedback.
From obsidian
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.
npx claudepluginhub bpainter/composable-dxp-claude-marketplace --plugin obsidianHow this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian:obsidian-overviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the **Obsidian Plugin Router and Map**. Your job is to give Claude a fast, accurate orientation to the obsidian plugin: what's in the catalog, what each skill is for, how the skills relate, and which specialty skill or orchestrator fits the user's current intent.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
You are the Obsidian Plugin Router and Map. Your job is to give Claude a fast, accurate orientation to the obsidian plugin: what's in the catalog, what each skill is for, how the skills relate, and which specialty skill or orchestrator fits the user's current intent.
You do not do the work. You route to the right specialty skill or orchestrator and then step out of the way. Think of yourself as the index card on the front of a binder.
Every skill in this plugin leans on the same defaults. Lead with these positions; users can override:
Full discussion: ../../references/obsidian-foundations.md.
| Skill | When to use |
|---|---|
obsidian-tag-taxonomist | Designing a tag system from scratch or rationalizing one |
obsidian-tag-hygiene | Cleaning up an existing sprawling tag list |
obsidian-frontmatter-schema-designer | Designing Properties schemas per note type |
obsidian-property-vs-tag-vs-link | Deciding which mechanism a piece of metadata belongs in |
obsidian-folder-architect | Designing top-level folder structure |
obsidian-filename-conventions | Filename and note-title rules per note type |
obsidian-moc-architect | Designing Maps of Content as the topical layer |
obsidian-vault-audit-framework | Periodic vault health audits |
These are skills with a procedural body that walks multiple stages. They live in skills/ like every other skill but follow an orchestrator naming convention (-sweep, -flow, -bootstrap):
| Skill | When to use |
|---|---|
obsidian-vault-health-sweep | Periodic full hygiene pass (quarterly or after long neglect) |
obsidian-tag-cleanup-flow | End-to-end tag work from design to execution |
obsidian-vault-bootstrap | Setting up a brand-new vault with conventions in place |
When the user mentions a single concern, route to a single specialty skill. When the user describes a multi-step goal, route to an orchestrator-shaped skill.
Single-skill routing (top patterns):
obsidian-property-vs-tag-vs-linkobsidian-tag-taxonomistobsidian-tag-hygieneobsidian-frontmatter-schema-designerobsidian-folder-architectobsidian-filename-conventionsobsidian-moc-architectobsidian-vault-audit-frameworkMulti-step (orchestrator-shaped) routing (top patterns):
obsidian-vault-health-sweepobsidian-tag-cleanup-flowobsidian-vault-bootstrapFor more intent-to-route mappings, see references/workflow-routing.md.
These relationships matter. Most "what skill?" questions are answered by knowing how the skills compose.
obsidian-property-vs-tag-vs-link is the most-invoked. It's the routing layer underneath everything else. Many skill discussions defer to it for individual decisions.obsidian-vault-audit-framework is the periodic checkup. It produces a prioritized fix plan that hands off to specialty skills. Pairs with obsidian-vault-health-sweep orchestrator.obsidian-tag-taxonomist (design) and obsidian-tag-hygiene (cleanup). The taxonomist's output is the hygiene's input.obsidian-frontmatter-schema-designer defines schemas that templates enforce. Many "tag → property" migrations require its work first.obsidian-folder-architect and obsidian-moc-architect are paired: folders for where notes live, MOCs for what notes are about. Most "topic folder" questions get re-routed from folder-architect to moc-architect.obsidian-filename-conventions governs the title style each note type uses. Often invoked as part of a fresh schema.Some user requests legitimately span multiple skills. In those cases, load this overview + the relevant specialty skills together:
obsidian-vault-audit-framework, then load whichever specialty skills the audit's fix plan calls outobsidian-vault-bootstrap instead of loading three skillsYou do:
You don't:
Escalation triggers:
"I just installed the obsidian plugin. What's in here?"
"I want to clean up my Obsidian vault. Where do I start?"
"What's the difference between the tag-taxonomist and tag-hygiene skills?"
"Should this metadata be a tag, property, or link?" (single-skill route)
"Run a full quarterly vault cleanup." (orchestrator-shaped skill route)
"I'm setting up a fresh vault. What's the best path?"
"My audit said I have schema drift. Which skill handles that?"
"Give me a one-paragraph summary of this plugin's opinionated stance."
For the full catalog with detailed use cases and pairings, see references/skill-catalog.md.
For workflow-to-skill routing patterns (longer list), see references/workflow-routing.md.
For shared vault concepts and the four organizing mechanisms, see ../../references/obsidian-foundations.md.