obsidian-markdown

Create and edit Obsidian Flavored Markdown notes with wikilinks, embeds, callouts, and frontmatter.

178|24|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection --skill obsidian-markdown-zhanlincui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-markdown
Source: https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection/tree/main/obsidian-markdown
Command: npx skills add https://github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection --skill obsidian-markdown-zhanlincui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian users and AI agents often struggle to create and edit notes that conform to Obsidian's Flavored Markdown, including wikilinks, embeds, callouts, and frontmatter. This skill provides a reliable way to generate and adjust Obsidian-ready content so notes remain consistent and fully render in Obsidian.

Core Features & Use Cases

  • Obsidian syntax support: wikilinks, embeds, callouts, properties (frontmatter), tags, and other Obsidian-specific syntax.
  • Vault-focused editing: maintain link integrity and metadata while transforming or creating notes.
  • Use Case: Convert a plain Markdown draft into an Obsidian-ready note with working wikilinks and properly structured frontmatter.

Quick Start

Convert the provided Markdown file to Obsidian-flavored Markdown with wikilinks, embeds, callouts, and frontmatter support, preserving existing links and tags.

Frequently Asked Questions about obsidian-markdown

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

FAQPage Schema
How do I convert plain Markdown to Obsidian Flavored Markdown with wikilinks and frontmatter?

Obsidian Flavored Markdown extends standard syntax by adding wikilinks for internal linking, callouts for blockquotes, embeds for transclusions, and YAML frontmatter for metadata. This syntax enables reliable formatting and link consistency across documents within an Obsidian vault.

How do I maintain frontmatter integrity and link consistency when editing Obsidian notes?

You maintain frontmatter integrity and link consistency by applying vault-focused editing rules that preserve Obsidian-specific syntax during transformations. This approach ensures metadata properties and wikilinks remain intact and fully render in Obsidian.

Does this approach support Obsidian embeds, callouts, and tags without breaking existing syntax?

Yes, the process explicitly supports Obsidian-specific embeds, callouts, and tags. It is designed to preserve these syntax elements alongside frontmatter and wikilinks, ensuring safe rendering across all documents in an Obsidian vault.

What is the best way to generate Obsidian-ready notes from an existing Markdown draft?

The best way to generate Obsidian-ready notes is to transform the draft by applying Obsidian Flavored Markdown rules, converting standard links to wikilinks, and structuring metadata into frontmatter. This ensures the note fully renders in Obsidian.

When do I need to use Obsidian-specific syntax like wikilinks and callouts instead of standard Markdown?

You need Obsidian-specific syntax like wikilinks and callouts when working within Obsidian vaults that require internal document linking, block transclusions, and styled blockquotes. This ensures reliable formatting and link consistency across your notes.