obsidian-markdown

Create and edit Obsidian-flavored Markdown notes with wikilinks, embeds, and frontmatter.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/officechbusinessservices-creator/CompliCore --skill obsidian-markdown-officechbusinessservices-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-markdown
Source: https://github.com/officechbusinessservices-creator/CompliCore/tree/main/.agents/skills/obsidian-markdown
Command: npx skills add https://github.com/officechbusinessservices-creator/CompliCore --skill obsidian-markdown-officechbusinessservices-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Obsidian users often struggle to consistently apply Obsidian-specific syntax (wikilinks, embeds, callouts, and frontmatter) across notes, causing formatting inconsistencies and reduced vault readability.

Core Features & Use Cases

  • Create and edit Obsidian Flavored Markdown that supports wikilinks, embeds, callouts, and frontmatter metadata.
  • Use in vault-wide note-taking workflows to connect related notes, embed media, and manage Obsidian-specific properties.
  • Example: draft a note with a wikilink to [[Daily Journal]], embed an image using ![[image.png]], and attach YAML frontmatter for tags and aliases.

Quick Start

Create a simple Obsidian note with frontmatter, a wikilink, and an embedded image to verify 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 Markdown notes with wikilinks and embeds?

Obsidian Markdown notes use wikilinks like [[Note Title]] to connect related files and ![[image.png]] to embed media. You can also attach YAML frontmatter to manage tags and aliases for consistent vault workflows.

What is the syntax for Obsidian callouts and frontmatter properties?

Obsidian callouts and frontmatter properties are specific Markdown extensions that format alert blocks and metadata. This Skill supports generating these syntax elements to maintain formatting consistency and readability across your vault.

Can I use standard Markdown or do I need Obsidian-flavored syntax for vault workflows?

For vault workflows requiring internal links and media embeds, you need Obsidian-flavored Markdown. This approach supports wikilinks, embeds, and Obsidian properties syntax that standard Markdown does not handle natively.

How do I embed an image and link to a daily journal in Obsidian Markdown?

To embed an image and link to a daily journal in Obsidian Markdown, use the embed syntax ![[image.png]] for media and the wikilink [[Daily Journal]] to connect related notes. This ensures proper rendering and connectivity within your vault.

Why does my Obsidian Markdown formatting break when using standard Markdown editors?

Standard Markdown editors often lack support for Obsidian-specific syntax like wikilinks, embeds, and frontmatter properties. Using a tool designed for Obsidian-flavored Markdown ensures these internal links and metadata render correctly in your vault.

What are the limitations of generating Obsidian Markdown syntax automatically?

Generating Obsidian Markdown syntax requires strict adherence to wikilink and embed formats to avoid rendering issues. While frontmatter, callouts, and properties are supported, complex vault-wide structural dependencies may still need manual verification.