obsidian-markdown

Writes correct Obsidian Flavored Markdown syntax for wiki pages including wikilinks, embeds, callouts, and frontmatter.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill obsidian-markdown-thedougler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obsidian-markdown
Source: https://github.com/Thedougler/shattered-sea-wiki/tree/main/.claude/skills/obsidian-markdown
Command: npx skills add https://github.com/Thedougler/shattered-sea-wiki --skill obsidian-markdown-thedougler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Obsidian Flavored Markdown incorrectly causes broken wikilinks, invisible callouts, malformed frontmatter, and duplicated content across a vault. This Skill provides the exact syntax rules and conventions needed to create or edit any wiki page correctly the first time. ## Core Features & Use Cases - Wikilinks and Embeds: Covers internal link syntax, aliased links, heading and block links, and embeds for notes, images, PDFs, audio, and canvases. - Callouts and Formatting: Documents all built-in callout types, custom D&D play callouts (read-aloud, secret, skill-check), collapsible variants, plus highlights, math, Mermaid diagrams, and footnotes. - Frontmatter and DRY Patterns: Enforces flat YAML properties, correct date and tag formats, and dynamic content patterns like base embeds and section embeds to avoid duplication. - Use Case: When drafting a new NPC page for a campaign wiki, reference this Skill to write valid frontmatter, link related entities with wikilinks, and add a read-aloud callout that renders correctly in Obsidian. ## Quick Start Ask the agent to create a new wiki page for an NPC using correct Obsidian syntax with wikilinks, a read-aloud callout, and proper frontmatter.

Frequently Asked Questions about obsidian-markdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create internal links in Obsidian Markdown?▼

Use double brackets with the note filename, like [[Note Name]]. Add a pipe for display text ([[Note Name|Display Text]]), a hash for headings ([[Note Name#Heading]]), or a folder path to disambiguate duplicate filenames.

How do I add callouts in Obsidian notes?▼

Write a blockquote with a type keyword: > [!note] followed by the content. Obsidian supports built-in types like warning, tip, and question, plus collapsible variants using a minus or plus sign after the type.

What frontmatter format does Obsidian require?▼

Obsidian requires flat YAML with no nested objects, dates in YYYY-MM-DD format, lists written as dash items rather than inline brackets, and wikilinks quoted as strings like "[[Page]]". The tags field is read as the note's searchable tag list.

Why is my Obsidian callout not rendering?▼

Callouts fail when headings are placed inside the callout body, HTML is used instead of Markdown, or the type keyword is misspelled. Keep callout content as plain Markdown blockquote lines starting with >.

When should I use embeds instead of wikilinks in Obsidian?▼

Use embeds (![[Note]]) to display content inline, such as a section from another page or a base query that updates automatically. Use plain wikilinks when the reader should click through to the full page, avoiding duplicated static content.