obsidian

Create Obsidian Document

Write a well-formatted markdown note to an Obsidian vault.

Vault Path Resolution

Resolve the vault path using this priority order:

1. Environment variable — check OBSIDIAN_VAULT_PATH. If set, use it directly.
2. User prompt — if the env var is not set, use AskUserQuestion to ask:

   What is the path to your Obsidian vault? (e.g., ~/Documents/MyVault)

Cache the resolved path for the remainder of the session.

Workflow

1. Parse the user's request for:

   • Topic/title — what the note is about
   • Subfolder — optional path within the vault (e.g., guides/)
   • Content direction — what the note should cover

2. If the vault or topic is ambiguous, use AskUserQuestion to clarify:

   • Any subfolder structure preference
   • Scope of content

3. Check the target vault for existing structure:

   ls "<vault-path>/"
   

   Respect existing folder conventions. If the vault uses dated folders, date-prefixed filenames, or topic folders — follow suit.

4. Check for an existing note with the same or similar name to avoid duplicates:

   find "<vault-path>" -iname "*<keyword>*" -name "*.md"
   

5. Write the note using the Write tool. Path format:

   <vault-path>/<optional-subfolder>/<Title>.md
   

Note Formatting Rules

• Use standard markdown compatible with Obsidian's renderer
• Start with a # Heading matching the filename
• Use ## Sections for logical groupings
• Fenced code blocks with language identifiers
• Pipe tables for structured data
• Use [[wikilinks]] for cross-references within the same vault when relevant
• No YAML frontmatter unless the user requests it or the vault has an established frontmatter convention
• No emojis unless the user requests them

Guidelines

• Read before writing — check if a similar note exists; offer to update instead
• Match vault conventions — if the vault has a pattern (folders, naming, tags), follow it
• One idea per note — prefer focused notes over mega-documents
• Keep it scannable — headings, lists, and code over prose walls
• Confirm on ambiguity — when unsure about vault, scope, or structure, ask