How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian:obsidian_commandsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Core infrastructure for the obsidian: command namespace. Provides:
Core infrastructure for the obsidian: command namespace. Provides:
This module is the foundation for CLI restructuring in v1.0.0:
obsidian_commands/
├── __init__.py # Package exports
├── router.py # Command routing logic
└── SKILL.md # This file
All commands use the obsidian: prefix:
| Command | Description | Subcommands |
|---|---|---|
obsidian:init | Initialize vault | - |
obsidian:config | Configuration management | show, edit, validate, methodologies |
obsidian:types | Note type management | list, show, add, edit, remove, wizard |
obsidian:props | Property management | core, type, required, add, remove |
obsidian:templates | Template management | list, show, create, edit, delete, apply |
obsidian:validate | Vault validation | - |
from obsidian_commands import route_command
# Route a command
exit_code = route_command("obsidian:config", ["show", "--vault", "/path"])
# List all commands
uv run skills/obsidian_commands/router.py --list
This skill is not user-facing. It provides internal routing infrastructure for the obsidian: command namespace. Users interact with individual skills (config, validate, init, etc.) through their slash commands - this module handles the dispatch behind the scenes.
It is intentionally not listed in plugin.json's skills array.
npx claudepluginhub wep4you/wep4you-agent-skills --plugin obsidianGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.