obsidian-markdown is a compact reference Claude uses when you ask for Obsidian-specific note formatting. It covers flat YAML properties, wikilinks with headings and block references, embeds, callouts, tags, comments, highlights, math and Mermaid.
Syntax questions are answered read-only. If you ask for a vault edit, the note is drafted whole, checked, and written through one inspected transaction that also updates the active index.
What You Get
- Correct frontmatter with flat properties, ISO dates and quoted wikilinks
- Wikilink, heading, block reference and embed forms with the right syntax
- Callout types with collapsed and expanded markers
- A validation checklist for drafted notes
- A single reviewed transaction when a note is written to the vault
Common Use Cases
- Asking how to embed a note section or a PDF page
- Drafting a source note with valid properties and links
- Checking a note for broken fences, tags and callouts before saving
What Makes It Unique
It is scoped to Obsidian-specific syntax and defers to the separately installed kepano obsidian-markdown skill and the official help for detailed or version-sensitive questions. Writes never bypass the plugin’s transaction engine, and a new or removed canonical page is paired with an index update in the same bundle.
Under The Hood
The skill is instructions with inline examples and links to the plugin’s transaction and provenance references. Answering a syntax question uses no tools. For a requested note edit it runs the plugin’s Python core script through the shell to inspect and apply a transaction bundle, writing only under wiki/ after you approve the plan hash. It does not fetch web pages or call outside services.