obsidian_markdown

Generate Obsidian-specific Markdown with wikilinks, embeds, callouts, and YAML properties.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill obsidian-markdown-antonyfmunoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian_markdown
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/obsidian_markdown
Command: npx skills add https://github.com/antonyfmunoz/OS --skill obsidian-markdown-antonyfmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken vault navigation and formatting by guiding you to use Obsidian-specific Markdown features correctly within the OS vault.

Core Features & Use Cases

  • Internal linking (wikilinks): Use [[Note]] syntax for rename-safe, bidirectional-style navigation inside the vault.
  • Embeds & transclusion: Use ![[Note]] to inline content (including headings, block IDs, images, PDFs, audio, and more) where appropriate.
  • Obsidian UI primitives: Apply callouts (> [!type]), properties (YAML frontmatter), tags (#tag), comments (%% %%), highlights (== ==), and diagrams (mermaid).
  • Vault hygiene & integration: Follow EOS backlink/linking rules and run the backlink audit script when needed to maintain link health.

Quick Start

Ask me to create a new vault note in /opt/OS/knowledge named "Project Alpha" with YAML frontmatter, wikilinks to related notes, an ![[embed]] section, and a properly formatted callout for key deadlines.

Frequently Asked Questions about obsidian_markdown

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

FAQPage Schema
How do I write Obsidian Markdown with correct wikilinks and YAML frontmatter?

To write Obsidian Markdown correctly, structure notes with YAML frontmatter properties first, then use [[wikilinks]] for internal navigation and ![[embeds]] for transclusion to maintain vault consistency.

What is the best way to create Obsidian callouts and embeds in my knowledge base?

Creating Obsidian callouts and embeds involves using specific syntax like > [!type] for callouts and ![[Note]] for inline transclusion of headings, block IDs, and media files within your knowledge base.

How do I use frontmatter properties and tags in Obsidian markdown notes?

Using frontmatter properties requires placing YAML metadata at the top of the markdown note, while tags can be applied inline using #tag syntax to ensure proper categorization and filtering in Obsidian.

Why are my Obsidian wikilinks breaking and how do I fix vault navigation?

Broken Obsidian wikilinks happen when standard markdown links replace [[wikilinks]], causing navigation failures; fixing this requires updating syntax and running a backlink audit script to restore link health.

Can I use standard markdown syntax instead of wikilinks for internal vault navigation?

Standard markdown links are not recommended for internal vault navigation because they lack bidirectional linking and rename-safety, whereas [[wikilinks]] ensure consistent backlinks and structural integrity.

Does Obsidian markdown support block IDs and mermaid diagrams for knowledge base notes?

Obsidian markdown supports block IDs for granular linking and mermaid code blocks for rendering diagrams, allowing complex knowledge base notes to integrate visual and structural data natively.