obsidian-markdown

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

2|Updated Jun 1, 2017
One-click install
npx skills add https://github.com/carlos-algms/dotfiles --skill obsidian-markdown-carlos-algms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-markdown
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/obsidian-markdown
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill obsidian-markdown-carlos-algms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you produce correct Obsidian Flavored Markdown instead of guesswork, so your notes render properly with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.

Core Features & Use Cases

  • Wikilinks and linking: Use [[Note]], [[Note|Text]], heading links, and block IDs to connect notes inside a vault without broken navigation.
  • Embeds and rich inserts: Embed notes, headings, images, and PDFs using ![[...]] for inline context.
  • Callouts and frontmatter: Add callouts like > [!warning] and define properties via YAML frontmatter to drive organization and search.

Quick Start

Ask the skill to convert your draft note into valid Obsidian Flavored Markdown with wikilinks, optional YAML frontmatter properties, at least one embed, and one callout.

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 embeds?

To write Obsidian markdown correctly, use [[Note]] syntax for wikilinks and ![[...]] for inline embeds. This ensures notes, headings, images, and PDFs render properly and connect without broken navigation inside your vault.

What is the syntax for Obsidian callouts and YAML frontmatter properties?

Obsidian callouts use the > [!type] syntax, such as > [!warning], to render distinct UI blocks. YAML frontmatter properties are defined at the note's start to drive vault organization, search, and metadata tagging.

How do I link to a specific heading or block ID in an Obsidian note?

Linking to specific headings or block IDs in an Obsidian note uses extended wikilink syntax like [[Note#Heading]] or [[Note^block-id]]. This connects precise sections inside a vault without causing broken navigation.

Can I convert a plain text draft into valid Obsidian Flavored Markdown?

You can convert plain text drafts into valid Obsidian Flavored Markdown by applying correct formatting rules. This process adds wikilinks, optional YAML frontmatter properties, embeds, and callouts to ensure vault readiness.

Does Obsidian markdown support advanced features like Mermaid diagrams and footnotes?

Obsidian markdown supports optional advanced features including Mermaid node linking, footnotes, block IDs, and comments. Applying these specific syntax rules correctly ensures complex vault notes render without formatting errors.

Why are my Obsidian embeds and wikilinks not rendering correctly in vault notes?

Embeds and wikilinks fail to render when Obsidian formatting rules are applied incorrectly. Valid Obsidian Flavored Markdown requires precise ![[embed]] syntax for rich inserts and exact [[Note]] structures for navigation.