writing-note

# Obsidian Notes If `$ARGUMENTS` is provided, treat it as the user's note request and proceed directly without asking for clarification. ## Overview Standard operations for reading, writing, and organizing notes in the Obsidian vault (Obsidian Flavored Markdown with YAML frontmatter and wikilinks). All vault operations use Obsidian MCP tools with vault-relative paths. ## Companion Skills Obsidian supports more than plain markdown notes. Before proceeding, consider whether the user's request is better served by one of these formats: | Skill | Format | When to use | |-------|--------|-------------| | `obsidian-markdown` | `.md` | **Always invoke** when creating or editing notes — ensures correct Obsidian Flavored Markdown (wikilinks, callouts, embeds, properties) | | `obsidian-bases` | `.base` | User wants a database view, filtered table, card gallery, or summary of notes by properties | | `json-canvas` | `.canvas` | User wants a visual layout — mind map, flowchart, project board, or spatial arrangement of ideas | Invoke the relevant skill(s) before writing content so you follow the correct syntax. ## Directory Structure Top-level categories: `Work/`, `Dev/`, `Games/`, `Personal/`, `Travel/`, `DailyNote/` - Max depth: **3 levels** for general notes - Exception: Projects and Meetings allow **4 levels** ## Special Note Types (use templates) | Type | Path pattern | Template | |------|-------------|----------| | Project | `Work/Projects/[ProjectName]/[ProjectName].md` |...