obsidian-markdown

Enforce Obsidian-flavored Markdown syntax and frontmatter standards across notes.

7|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Zpankz/mcp-skillset --skill obsidian-markdown-zpankz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-markdown
Source: https://github.com/Zpankz/mcp-skillset/tree/main/obsidian-markdown
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill obsidian-markdown-zpankz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Enforces Obsidian-flavored Markdown syntax across notes to prevent formatting drift, ensuring frontmatter integrity and consistent internal references.

Core Features & Use Cases

  • YAML frontmatter validation and kebab-case property naming across notes.
  • Wikilinks, callouts, tables, mermaid diagrams, and Dataview/Templater syntax compatibility.
  • Reliable templates and content patterns for daily notes, MOCs, and project notes.

Quick Start

Create a new note with valid YAML frontmatter and Obsidian syntax, then add content that uses wikilinks and callouts.

Frequently Asked Questions about obsidian-markdown

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

FAQPage Schema
How do I validate YAML frontmatter and enforce kebab-case properties in Obsidian notes?

You can validate YAML frontmatter and enforce kebab-case property naming by applying Obsidian-flavored Markdown standards that check structural integrity and ensure consistent property formatting across notes.

Does Dataview syntax work correctly when formatting MOCs and project notes in Obsidian?

Yes, Dataview syntax compatibility is supported when formatting MOCs and project notes, ensuring integration-ready patterns that maintain reliable content structures and query execution within your vault workflows.

What is the best way to standardize wikilinks and callouts across an Obsidian vault?

The best way to standardize wikilinks and callouts is to enforce Obsidian-flavored Markdown syntax rules that prevent formatting drift and guarantee consistent internal references throughout your daily notes and templates.

Can I use this approach to fix formatting drift in Obsidian templates created with Templater?

Yes, you can fix formatting drift in Templater templates by enforcing proper code blocks and integration-ready patterns designed specifically for reliable daily notes, MOCs, and project notes creation.

Why does my Obsidian markdown structure break when combining mermaid diagrams and tables?

Obsidian markdown structure breaks because standard formatting lacks enforced syntax rules for complex elements like mermaid diagrams and tables, which requires applying specific Obsidian-flavored standards to maintain compatibility.

When do I need to enforce Obsidian markdown syntax instead of using standard markdown?

You need to enforce Obsidian markdown syntax instead of standard markdown when your vault relies on specialized features like wikilinks, frontmatter, callouts, Dataview queries, and Templater scripts that require strict structural validation.