Generate Obsidian Flavored Markdown

Obsidian Flavored Markdown Skill explains the syntax Obsidian adds to CommonMark and GitHub Flavored Markdown. It covers internal wikilinks, note and file embeds, callouts, YAML frontmatter properties, tags, comments, highlights, math, Mermaid diagrams, and footnotes. Standard headings, lists, emphasis, quotes, tables, and code blocks are treated as prior Markdown knowledge.

Use the guide when writing or editing Markdown intended for an Obsidian vault, especially when notes need internal links, embeds, callouts, properties, or syntax that renders specially in Obsidian. It recommends wikilinks for notes inside the vault because Obsidian can track renames, and ordinary Markdown links for external destinations. The workflow ends by checking the note in Obsidian's reading view.

Inputs include note content, title, tags, aliases, related files, and the desired structure. The output is a Markdown note with YAML properties at the top and Obsidian-specific syntax in the body. Properties can be text, numbers, checkboxes, dates, date-times, lists, and links. Tags can be inline or defined in frontmatter; nested tags use slash-separated hierarchy, while tag names can also include underscores and hyphens.

An internal note link from the source is:

[[Note Name|Display Text]]

Wikilinks can point to a note, a heading, a block ID such as [[Note#^block-id]], or a heading in the current note. Embeds place note sections, block IDs, images, audio, PDFs, lists, or search results inline; PDF embeds can target #page=3, and query embeds use a fenced query block. Callouts use a block quote marker and a bracketed type such as note, warning, tip, question, or example. Aliases include faq for question, caution for warning, and tldr for abstract. A trailing - folds a callout closed by default and + opens it; callouts can also nest.

The source references Obsidian's reading and editing views, its vault link tracking, YAML frontmatter, and Mermaid diagrams. It includes hidden comments delimited by percent signs, highlighted text using paired equals signs, inline and block LaTeX, and Mermaid flowcharts. Embeds include local notes and media, plus external images using standard Markdown image syntax. The workflow recommends adding properties, writing with standard Markdown plus the required extensions, linking related notes, embedding files as needed, and confirming rendering in the reading view.

Reference sections distinguish text, number, checkbox, date/time, list, and link properties; common defaults include tags, aliases, and cssclasses. Embed variants include local and external images, audio, PDF pages, list blocks, and search queries. Hidden comments use %%...%%, highlight uses ==...==, and math uses inline or block LaTeX. The guide's scope is limited to Obsidian-specific extensions and does not replace general Markdown knowledge.

Obsidian users, note authors, and knowledge-management teams can use the reference to create consistent notes that render and link as intended inside a vault.