obsidian-markdown

Obsidian Flavored Markdown Skill

Create and edit valid Obsidian Flavored Markdown. Obsidian extends CommonMark and GFM with wikilinks, embeds, callouts, properties, comments, and other syntax. This skill covers only Obsidian-specific extensions -- standard Markdown (headings, bold, italic, lists, quotes, code blocks, tables) is assumed knowledge.

Property Discipline

Prefer Obsidian-native properties and file metadata before adding custom frontmatter.

• Use native properties (tags, aliases, cssclasses) when they fit the request.
• Use the note file name, folder, links, backlinks, tags, created/modified time, and other Obsidian file metadata instead of duplicating them into custom properties.
• Do not add custom properties such as title, status, date, priority, due, category, or type unless the user asks for those fields, an existing vault convention already uses them, or another requested feature needs structured data that Obsidian cannot infer natively.
• When editing an existing note, preserve existing properties and only add new ones when needed for the user's requested workflow.

Workflow: Creating an Obsidian Note

1. Decide whether frontmatter is needed. If no structured metadata is required, start directly with Markdown content. If properties are needed, prefer native Obsidian properties first. See PROPERTIES.md for all property types.
2. Write content using standard Markdown for structure, plus Obsidian-specific syntax below.
3. Link related notes using wikilinks ([[Note]]) for internal vault connections, or standard Markdown links for external URLs.
4. Embed content from other notes, images, or PDFs using the ![[embed]] syntax. See EMBEDS.md for all embed types.
5. Add callouts for highlighted information using > [!type] syntax. See CALLOUTS.md for all callout types.
6. Verify the note renders correctly in Obsidian's reading view.