Stop manually organizing your Obsidian vault. This skill teaches Claude to migrate, enrich, and restructure your notes — reading each one, assigning properties based on content, renaming to your conventions, and updating every link automatically. You review a proposal, approve it, and watch hundreds of notes get organized in minutes.

Every Obsidian CLI command is documented in its own reference file. The skill uses progressive disclosure — only loading the reference it needs for your specific request — so the model always has precise, complete command syntax without bloating the context window.

# In Claude Code terminal:
/plugin marketplace add cwaits6/obsidian-cli-skill
/plugin install obsidian-cli@obsidian-cli-skill

Then just ask:

Migrate all my notes from Research/ to Notes/ with automatic property assignment

• Migrate and enrich notes — reads content, assigns type/context/topic properties, renames to your convention, moves to the right folder, updates all links
• Create Obsidian Bases — generates .base files that query your notes by properties for structured views
• Generate Templater templates — builds templates with dynamic syntax for automating note creation
• Bulk operations — rename, move, delete, or update properties across hundreds of files
• Search and analyze — find notes by content, trace link structure, surface orphans and broken links
• Manage plugins and themes — enable, disable, install via CLI

Every operation follows the same approval workflow:

1. Analyze — Claude reads your notes and config
2. Propose — you see exactly what will happen before anything changes
3. Approve — you say yes (or adjust)
4. Execute — commands run via Obsidian CLI

Step 1: Claude proposes property assignments for each note

Step 2: Claude proposes renames and destination folder

Step 3: Migration complete with summary

Large operations run through a dedicated batch executor agent that processes files in chunks, so you get progress feedback throughout and can approve per-batch or per-note. Batch size is configurable.

Copy the example config and customize for your vault:

# Path will match wherever Claude Code installed the plugin
cp ~/.claude/plugins/marketplaces/obsidian-cli-skill/plugins/obsidian-cli/config.yaml.example \
   ~/.claude/plugins/marketplaces/obsidian-cli-skill/plugins/obsidian-cli/config.yaml

The config defines your property schema (types, contexts, topics), naming conventions, and batch settings. See config.yaml.example for all options.

Your config.yaml is gitignored — plugin updates won't overwrite it.

/plugin marketplace update

• Obsidian 1.12.2 or later with CLI enabled (Settings → General → Advanced → Command line interface) — requires a Catalyst license
• Claude Code with plugin support

Contributions welcome! See CONTRIBUTING.md for guidelines.

See CHANGELOG.md for version history.

MIT License — see LICENSE for details.