Skip to content
SkillModel-led1,066 tokens in use

obsidian-markdown

Explains, drafts and validates Obsidian Flavored Markdown: properties, wikilinks, embeds, callouts, math and Mermaid.

16,653 stars on the repository MIT LicenseAgriciDaniel/claude-obsidian · skills/obsidian-markdown
claude plugin marketplace add AgriciDaniel/claude-obsidian claude plugin install claude-obsidian@agricidaniel-claude-obsidian
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing obsidian-markdown costs

69tokens idle
1,066tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure9/25
  • Examples15/15
  • Output10/15
  • Size10/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 17

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity84
  • Maintenance100
  • Community56
  • Maturity28
  • Momentum40

obsidian-markdown is a compact reference Claude uses when you ask for Obsidian-specific note formatting. It covers flat YAML properties, wikilinks with headings and block references, embeds, callouts, tags, comments, highlights, math and Mermaid.

Syntax questions are answered read-only. If you ask for a vault edit, the note is drafted whole, checked, and written through one inspected transaction that also updates the active index.

What You Get

  • Correct frontmatter with flat properties, ISO dates and quoted wikilinks
  • Wikilink, heading, block reference and embed forms with the right syntax
  • Callout types with collapsed and expanded markers
  • A validation checklist for drafted notes
  • A single reviewed transaction when a note is written to the vault

Common Use Cases

  • Asking how to embed a note section or a PDF page
  • Drafting a source note with valid properties and links
  • Checking a note for broken fences, tags and callouts before saving

What Makes It Unique

It is scoped to Obsidian-specific syntax and defers to the separately installed kepano obsidian-markdown skill and the official help for detailed or version-sensitive questions. Writes never bypass the plugin’s transaction engine, and a new or removed canonical page is paired with an index update in the same bundle.

Under The Hood

The skill is instructions with inline examples and links to the plugin’s transaction and provenance references. Answering a syntax question uses no tools. For a requested note edit it runs the plugin’s Python core script through the shell to inspect and apply a transaction bundle, writing only under wiki/ after you approve the plan hash. It does not fetch web pages or call outside services.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers