Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agricidaniel avatar

Obsidian Markdown

  • 395 installs
  • 10.4k repo stars
  • Updated August 1, 2026
  • agricidaniel/claude-obsidian

obsidian-markdown is an agent skill that formats notes as valid Obsidian Flavored Markdown with wikilinks, callouts, tags, and frontmatter for developers maintaining Obsidian vault documentation.

About

obsidian-markdown is an agent skill that teaches correct Obsidian Flavored Markdown when creating or editing vault pages. Standard Markdown alone breaks Obsidian-specific features, so the skill documents wikilinks, embeds, callouts, YAML properties, tags, highlights, math blocks, and canvas syntax with allowed-tools Read, Write, and Edit. Triggers include write obsidian note, wikilink format, callout syntax, embed syntax, and how to write obsidian markdown. Developers reach for it whenever an AI agent saves architecture notes, runbooks, or research pages into an Obsidian vault and need links, callouts, and frontmatter to render instead of showing raw broken syntax. The skill acts as a reference guardrail rather than a note-taking app itself, ensuring agent output matches Obsidian parser expectations.

  • Obsidian-specific markdown syntax
  • Wikilinks and callout blocks
  • YAML frontmatter handling
  • Tag and embed conventions
  • Vault-ready note structure

Obsidian Markdown by the numbers

  • 395 all-time installs (skills.sh)
  • Ranked #413 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/agricidaniel/claude-obsidian --skill obsidian-markdown

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs395
repo stars10.4k
Last updatedAugust 1, 2026
Repositoryagricidaniel/claude-obsidian

How do you write valid Obsidian wikilinks and callouts?

Format agent outputs as valid Obsidian markdown with wikilinks, callouts, tags, and frontmatter before saving notes into a vault.

Who is it for?

Developers using Obsidian vaults who want AI agents to output syntactically correct Obsidian Flavored Markdown instead of generic GitHub-flavored markdown.

Skip if: Documentation workflows targeting plain GitHub README or MkDocs sites without Obsidian wikilinks, callouts, or vault-specific syntax.

When should I use this skill?

The user asks to write an Obsidian note, format wikilinks, create callouts, embed files, or fix Obsidian markdown syntax in a vault.

What you get

Obsidian-compatible markdown files with wikilinks, embeds, callouts, properties, tags, and optional canvas or math blocks.

  • Obsidian-formatted markdown notes

By the numbers

  • Documents 8 Obsidian markdown extensions including wikilinks, callouts, embeds, and canvas syntax

Files

SKILL.mdMarkdownGitHub ↗

obsidian-markdown: Obsidian Flavored Markdown

Reference this skill when writing any wiki page. Obsidian extends standard Markdown with wikilinks, embeds, callouts, and properties. Getting syntax wrong causes broken links, invisible callouts, or malformed frontmatter.

Substrate preference (v1.7+): This skill is a self-contained fallback. Prefer `kepano/obsidian-skills` (by Steph Ango, Obsidian CEO) as the authoritative substrate — its obsidian-markdown skill is the canonical Obsidian syntax reference for any Agent-Skills runtime. If you see an obsidian-markdown skill available without the claude-obsidian: namespace, that is kepano's version: use it. The reference below is provided so the plugin remains functional when kepano's marketplace is not installed. Install: claude plugin marketplace add kepano/obsidian-skills. Repo: github.com/kepano/obsidian-skills.

---

Wikilinks

Internal links use double brackets. The filename without extension.

SyntaxWhat it does
[[Note Name]]Basic link
`[[Note Name\Display Text]]`
[[Note Name#Heading]]Link to a specific heading
[[Note Name#^block-id]]Link to a specific block

Rules:

  • Case-sensitive on some systems. Match the exact filename.
  • No path needed: Obsidian resolves by filename uniqueness.
  • If two files have the same name, use [[Folder/Note Name]] to disambiguate.

---

Embeds

Embeds use ! before the wikilink. They display the content inline.

SyntaxWhat it does
![[Note Name]]Embed a full note
![[Note Name#Heading]]Embed a section
![[image.png]]Embed an image
`![[image.png\300]]`
![[document.pdf]]Embed a PDF (Obsidian renders natively)
![[audio.mp3]]Embed audio

---

Callouts

Callouts are blockquotes with a type keyword. They render as styled alert boxes.

> [!note]
> Default informational callout.

> [!note] Custom Title
> Callout with a custom title.

> [!note]- Collapsible (closed by default)
> Click to expand.

> [!note]+ Collapsible (open by default)
> Click to collapse.

All callout types

TypeAliasesUse for
note:General notes
abstractsummary, tldrSummaries
info:Information
todo:Action items
tiphint, importantTips and highlights
successcheck, donePositive outcomes
questionhelp, faqOpen questions
warningcaution, attentionWarnings
failurefail, missingErrors or failures
dangererrorCritical issues
bug:Known bugs
example:Examples
quoteciteQuotations
contradiction:Conflicting information (wiki convention)

---

Properties (Frontmatter)

Obsidian renders YAML frontmatter as a Properties panel. Rules:

---
type: concept                    # plain string
title: "Note Title"              # quoted if it contains special chars
created: 2026-04-08              # date as YYYY-MM-DD (not ISO datetime)
updated: 2026-04-08
tags:
  - tag-one                      # list items use - format
  - tag-two
status: developing
related:
  - "[[Other Note]]"             # wikilinks must be quoted in YAML
sources:
  - "[[source-page]]"
---

Rules:

  • Flat YAML only. Never nest objects.
  • Dates as YYYY-MM-DD, not 2026-04-08T00:00:00.
  • Lists as - item, not inline [a, b, c].
  • Wikilinks in YAML must be quoted: "[[Page]]".
  • tags field: Obsidian reads this as the tag list, searchable in vault.

---

Tags

Two valid forms:

#tag-name             : inline tag anywhere in the body
#parent/child-tag     : nested tag (shows hierarchy in tag pane)

In frontmatter:

tags:
  - research
  - ai/obsidian

Do not use # inside frontmatter tag lists. Just the tag name.

---

Text Formatting

Standard Markdown plus Obsidian extensions:

SyntaxResult
**bold**Bold
*italic*Italic
~~strikethrough~~Strikethrough
==highlight==Highlighted text (yellow in Obsidian)
` inline code `Inline code

---

Math

Obsidian uses MathJax/KaTeX:

Inline math:

$E = mc^2$

Block math:

$$
\int_0^\infty e^{-x} dx = 1
$$

---

Code Blocks

Standard fenced code blocks. Obsidian highlights all common languages:

````markdown

def hello():
    return "world"

````

---

Tables

Standard Markdown tables:

| Column A | Column B | Column C |
|----------|----------|----------|
| Value    | Value    | Value    |
| Value    | Value    | Value    |

Obsidian renders tables natively. No plugin needed.

---

Mermaid Diagrams

Obsidian renders Mermaid natively:

````markdown

graph TD
    A[Start] --> B{Decision}
    B -->|Yes| C[End]
    B -->|No| D[Loop]
    D --> A

````

Supported: graph, sequenceDiagram, gantt, classDiagram, pie, flowchart.

---

Footnotes

This sentence has a footnote.[^1]

[^1]: The footnote text goes here.

---

What NOT to Do

  • Do not use [link text](path/to/note.md) for internal links: use [[Note Name]] instead.
  • Do not use HTML inside callouts: stick to Markdown.
  • Do not use ## inside a callout body: headings don't render inside callouts.
  • Do not write tags: [a, b, c] inline in frontmatter: Obsidian prefers the list format.
  • Do not write ISO datetimes in frontmatter (2026-04-08T00:00:00Z): use 2026-04-08.

---

How to think (10-principle mapping)

When working on this skill, apply the 10-principle loop. See `skills/think/SKILL.md` for the canonical framework.

#PrincipleApplication here
1OBSERVE (ext)Which syntax does the user need? (Wikilinks? Callouts? Embeds? Math? Mermaid?)
2OBSERVE (int)Am I documenting Obsidian Flavored Markdown as I remember it or as it currently is? Check the spec.
3LISTENThe user's source-of-confusion — what specific syntax did they get wrong?
4THINKMinimal correct examples. "What NOT to do" is often as valuable as "what to do."
5CONNECT (lat)How does OFM differ from CommonMark and GFM? The deltas are where users get confused.
6CONNECT (sys)Substrate-defer to kepano/obsidian-skills when present — single source of truth, less drift.
7FEELA cheat sheet that's scannable in 30 seconds, not a wall of text.
8ACCEPTNot every wikilink needs an alias; some syntax is genuinely optional. Don't over-prescribe.
9CREATESyntax reference, current to Obsidian X.Y. Include the gotchas section.
10GROWAs OFM evolves (newer Mermaid types, callout types, cssclasses, etc.), refresh.

Related skills

How it compares

Use obsidian-markdown instead of generic markdown skills when output must render inside Obsidian with wikilinks and callouts rather than standard CommonMark.

FAQ

Which Obsidian syntax does obsidian-markdown cover?

obsidian-markdown covers Obsidian Flavored Markdown including wikilinks, embeds, callouts, YAML properties, tags, highlights, math, and canvas syntax so agent-written vault pages render correctly.

When should an agent load obsidian-markdown?

An agent should load obsidian-markdown whenever creating or editing wiki pages in an Obsidian vault, especially when the user mentions wikilinks, callouts, embeds, or Obsidian-specific formatting.

Documentationnotesworkflow

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.