obsidian

Manage Obsidian vault configuration (settings.yaml)

Display help for all Obsidian vault management commands or get detailed information about a specific command.

Initialize a new Obsidian vault with a PKM methodology

Manage core and type-specific frontmatter properties.

Manage note templates with support for Templater plugin.

Manages YAML configuration files (settings.yaml, default.yaml) for Obsidian vaults via obsidian:config commands, settings_loader.py, and config_loader.py. Use this skill to inspect current vault config (obsidian:config show), validate config structure (obsidian:config validate), view config diffs from defaults (obsidian:config diff), edit settings (obsidian:config edit), create missing settings.yaml (obsidian:config create), list available methodologies, merge YAML overrides, check the config hierarchy (defaults vs vault-specific overrides), debug YAML parsing errors, or understand how settings_loader.py and config_loader.py work programmatically. Always consult for obsidian:config commands, settings.yaml questions, config file management, or methodology listings. This skill manages configuration files only — not frontmatter property schemas (use frontmatter), not note validation (use validate), not note type definitions (use note-types), not templates (use templates), not vault initialization (use init).

Manages frontmatter property definitions (schemas) for Obsidian vaults via obsidian:props commands and frontmatter.py CLI. Use this skill to add, remove, or list core properties (type, up, created, daily, collection, related) and type-specific properties (e.g. status for projects, author for sources, mood for dailies, tags for dots/maps), check which properties are required vs optional for a note type, change a property between required/optional, export property schemas as YAML or JSON, or understand the property type system (string, date, wikilink, list[string], list[wikilink]). Always consult this skill for obsidian:props commands, frontmatter property definitions, property schema questions, or when adding/removing fields from note types. This skill manages property definitions only — not note validation (use validate), not note-type creation (use note-types), not settings.yaml editing (use config), not templates (use templates).

Initializes a new Obsidian vault with a PKM methodology (LYT-ACE, PARA, Zettelkasten, or Minimal) via the obsidian:init command and init.py wrapper. Creates folder structure, settings.yaml configuration, sample notes, templates, Bases views, and Home.md. Use this skill whenever the user wants to create or initialize a new vault, set up a vault with a specific methodology, scaffold a PKM system, check vault initialization status (--check), list available methodologies (--list), reset or migrate an existing vault, or run obsidian:init. This is a multi-step interactive wizard — the skill contains the exact prompt_type flow and CLI flags needed. Always consult for vault initialization, vault setup, or methodology selection. This skill only handles initial setup — not ongoing config changes (use config), not validation (use validate), not template management (use templates), not note type changes after init (use note-types).

Manages note type definitions in Obsidian vaults via obsidian:types commands and note_types.py CLI — creating, editing, listing, and removing note types with their folder mappings, required/optional properties, icons, and template associations. MANDATORY: When user provides --config JSON, pass it EXACTLY as-is to the script — do NOT manually edit settings.yaml. Use this skill to define new note types (e.g. meeting, blog, book), view existing note types and their configurations, edit note type settings (folder, properties, icon, description), remove note types, run the interactive wizard, or set up folder-to-type mappings. Always consult for obsidian:types commands, note type CRUD operations, or questions about which note types exist and what they contain. This skill manages note type definitions only — not individual property schemas (use frontmatter), not note validation (use validate), not settings.yaml structure (use config), not note templates themselves (use templates).

Unified command router for Obsidian CLI commands