obsidian-markdown

Author and maintain Obsidian-flavored Markdown notes with wikilinks, embeds, callouts, and frontmatter.

54|18|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/open-fox/agents --skill obsidian-markdown-open-fox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-markdown
Source: https://github.com/open-fox/agents/tree/main/skills/obsidian-markdown
Command: npx skills add https://github.com/open-fox/agents --skill obsidian-markdown-open-fox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Obsidian users often struggle to create and edit notes that fully leverage Obsidian's extended Markdown features, leading to inconsistent formatting and metadata handling.

Core Features & Use Cases

  • Supports wikilinks [[Note]] for internal vault navigation, embeds ![[Note]] for inline content, and callouts > [!type] for highlighted information.
  • Handles frontmatter properties (title, tags, aliases) and standard Markdown content, enabling rich metadata and reliable search.
  • Ideal for building and maintaining a personal knowledge vault, drafting Obsidian notes, and ensuring consistent rendering across Obsidian.

Quick Start

Create a new Obsidian note with frontmatter, wikilinks, an embed, and a callout to verify Obsidian-specific rendering.

Frequently Asked Questions about obsidian-markdown

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

FAQPage Schema
How do I create Obsidian-flavored Markdown notes with frontmatter and wikilinks?

Create Obsidian-flavored Markdown notes by drafting standard content and adding frontmatter properties, wikilinks, embeds, and callouts to ensure consistent formatting and internal vault navigation. This approach preserves Obsidian extensions while maintaining common Markdown compatibility.

Does this approach support Obsidian callouts and embeds alongside standard Markdown content?

Yes, Obsidian callouts and embeds are fully supported alongside standard Markdown content. The formatting process enforces compatibility with common Markdown while preserving Obsidian extensions like embeds and callouts for highlighted information and inline content rendering.

What is the best way to maintain frontmatter properties like tags and aliases in a knowledge vault?

Maintain frontmatter properties by applying consistent metadata formatting for title, tags, and aliases across standard Markdown content. This enables reliable search and rich metadata structuring within an Obsidian vault, ensuring notes are properly indexed and linked.

How do I format internal vault navigation links using wikilinks?

Format internal vault navigation links using the wikilink syntax [[Note]] to connect notes within the vault. This preserves linking structures specific to Obsidian and enables seamless navigation between related Markdown notes without relying on standard URL paths.

Can I use this Markdown formatting method for building a personal knowledge vault?

Yes, this method is ideal for building and maintaining a personal knowledge vault. It handles vault-based workflows requiring wikilinks, embeds, callouts, and frontmatter properties, ensuring reliable search and consistent rendering across Obsidian notes.

Why does my Obsidian Markdown note lose its frontmatter and callout formatting?

Obsidian Markdown notes lose frontmatter and callout formatting when standard Markdown compatibility is not enforced alongside Obsidian extensions. Applying proper metadata formatting and preserving Obsidian-specific syntax ensures consistent rendering across the vault.