Obsidian Vault

This is Hermes's broad, generic entry point for Obsidian work. Keep using it for straightforward filesystem-first vault tasks such as locating the vault, listing notes, searching note files, creating notes, and appending content.

When the task is format-specific or app-specific, route to the specialized skills instead:

• .md note authoring with wikilinks, properties/frontmatter, callouts, embeds, or Obsidian-specific Markdown semantics -> obsidian-markdown
• running Obsidian app workflows, Obsidian CLI usage, plugin development, or theme development -> obsidian-cli
• editing .base files or working with Bases filters, views, and formulas -> obsidian-bases
• editing .canvas files or visual canvases -> json-canvas

Vault path

Use a known or resolved vault path before calling file tools.

The documented vault-path convention is the OBSIDIAN_VAULT_PATH environment variable, for example from ~/.hermes/.env. If it is unset, use ~/Documents/Obsidian Vault.

File tools do not expand shell variables. Do not pass paths containing $OBSIDIAN_VAULT_PATH to read_file, write_file, patch, or search_files; resolve the vault path first and pass a concrete absolute path. Vault paths may contain spaces, which is another reason to prefer file tools over shell commands.

If the vault path is unknown, terminal is acceptable for resolving OBSIDIAN_VAULT_PATH or checking whether the fallback path exists. Once the path is known, switch back to file tools.