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.06x

Quality

—

Does it follow best practices?

Impact

100%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is a thorough, actionable Obsidian syntax reference with concrete examples and a useful complete example note. Its main weaknesses are verbosity from restating standard Markdown basics and a monolithic structure that doesn't progressively disclose detail into separate files.

Suggestions

Remove or drastically condense sections covering standard Markdown Claude already knows (paragraphs, headings, bold/italic, basic lists, tables, fenced code) to free token budget for Obsidian-specific syntax.

Move the full callout-types reference table and the exhaustive syntax catalog into a separate reference file (e.g. references/syntax.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Add a short ordered workflow for authoring a new note (define properties → write content with wikilinks → add callouts/embeds → verify links resolve) to give the reference a clear procedural spine.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but sections like 'Paragraphs and Line Breaks', 'Headings', 'Text Styling', 'Lists', 'Tables', and 'Code Blocks' restate standard Markdown concepts Claude already knows, which the rubric penalizes; it could be tightened to focus on Obsidian-specific syntax.	2 / 3
Actionability	Provides concrete, copy-paste-ready syntax examples throughout (wikilinks, embeds, callouts, properties, math, mermaid) plus a complete end-to-end example note, matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	It is a syntax reference catalog rather than a sequenced multi-step process; the 'When to Use' list gives context but there is no ordered workflow with checkpoints, which fits the 'steps present but no real sequence' band for a non-procedural skill.	2 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a monolithic inline reference with no bundle files — content such as the full callout-types table and complete syntax catalog that could live in separate reference files is all inlined, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%

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

The description is specific, third-person, and clearly states both what the skill does and when to use it with natural trigger terms. It carves out a distinct Obsidian-specific niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities — 'Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax' — matching the anchor that lists several specific actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Create and edit Obsidian Flavored Markdown...') and when ('Use when working with .md files in Obsidian, or when the user mentions...'), with a clear 'Use when' clause.	3 / 3
Trigger Term Quality	Includes natural terms users would say — 'wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes' and '.md files in Obsidian' — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped specifically to Obsidian Flavored Markdown with distinct trigger terms (wikilinks, callouts, embeds), making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Commit: 366e45b

Reviewed: 2 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.