obsidian-markdown

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

1.19x

Quality

94%

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is obsidian-markdown in kepano/obsidian-skills

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, well-organized skill body: concise annotated examples, broad executable coverage of Obsidian syntax, and clean progressive disclosure to three real reference files. The only minor gap is the workflow's verify step, which could add an explicit fix-and-retry loop.

Suggestions

Strengthen the workflow's final step into an explicit validation feedback loop, e.g. "Verify in reading view; if a wikilink/embed is broken, fix the path or syntax and re-check."

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: terse annotated code blocks per section, explicitly defers standard Markdown as assumed knowledge, and avoids explaining what Obsidian is. Every section earns its tokens; not a 4 because there is no noticeable padding to trim.	5 / 5
Actionability	Fully executable, copy-paste-ready examples cover all common cases — wikilinks, embeds, callouts, properties YAML, tags, comments, math, mermaid, footnotes, plus a complete realistic example. Specific syntax variants are shown inline with labels.	5 / 5
Workflow Clarity	The "Workflow: Creating an Obsidian Note" gives a clear 6-step sequence with a terminal "Verify the note renders correctly" checkpoint. Not a 5 because the verify step lacks an explicit error-recovery/feedback loop; not a 3 because a concrete validation step is present and the operation is non-destructive so the cap does not apply.	4 / 5
Progressive Disclosure	Clear overview in SKILL.md with well-signaled, one-level-deep references to real files (PROPERTIES.md, EMBEDS.md, CALLOUTS.md, all present in references/); detailed enumerations are split out while core syntax stays inline, making navigation easy.	5 / 5
	Total	19 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description that clearly states capabilities and provides explicit, natural trigger conditions in third-person voice. The only soft spot is specificity, which could enumerate a few more discrete actions rather than feature categories.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates several concrete capabilities ("wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax") plus actions ("Create and edit"), with only minor gaps in coverage. Not a 5 because it does not list a comprehensive set of distinct concrete actions beyond create/edit.	4 / 5
Completeness	Explicitly answers both "what" ("Create and edit Obsidian Flavored Markdown with...") and "when" ("Use when working with .md files in Obsidian, or when the user mentions...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and file extensions: ".md files in Obsidian", "wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes" — these are exactly the phrases a user would say.	5 / 5
Distinctiveness Conflict Risk	Clear Obsidian-specific niche with distinct triggers (wikilinks, callouts, frontmatter, embeds) unlikely to fire for other skills; minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: breferrari/obsidian-mind
Path: .claude/skills/obsidian-markdown/SKILL.md
Commit: b84464b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.