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

90%

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

86%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 well-structured, highly actionable reference that assumes Claude's knowledge and offloads detail to genuine bundle files. The main improvement would be adding an error-recovery feedback loop to the verification step in the workflow.

Suggestions

Add a brief 'If the note does not render as expected, review the syntax and re-verify' feedback loop after the Verify step to reach a full validation cycle.

Trim the redundant embed syntax examples that repeat wikilink forms, or cross-reference the Wikilinks section to reduce duplication.

Consider shortening the Complete Example or marking it as optional, since it largely recombines syntax already shown above.

Dimension	Reasoning	Score
Conciseness	Mostly lean with code examples and an explicit statement that standard Markdown is assumed knowledge, though the Complete Example and some repeated embed syntax add length that could be trimmed slightly.	4 / 5
Actionability	Provides copy-paste-ready, executable code blocks for every syntax type (wikilinks, embeds, callouts, properties, tags, math, mermaid, footnotes) plus a full worked example covering common cases.	5 / 5
Workflow Clarity	A clear 6-step numbered workflow ends with an explicit 'Verify' checkpoint, but it lacks a feedback loop (fix-and-retry) for error recovery, stopping just short of the anchor 5.	4 / 5
Progressive Disclosure	The body is a well-organized overview with clearly signaled one-level-deep references to real bundle files (CALLOUTS.md, EMBEDS.md, PROPERTIES.md), keeping detail out of SKILL.md while remaining navigable.	5 / 5
	Total	18 / 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, third-person description that clearly states both capability and trigger conditions with good keyword coverage. The only slight gap is that 'Create and edit' compresses the action verbs relative to the breadth of features listed.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete capabilities (wikilinks, embeds, callouts, properties, other syntax) tied to 'Create and edit', with only minor coverage gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Explicitly states both what it does ('Create and edit Obsidian Flavored Markdown with ...') and when to use it ('Use when working with .md files in Obsidian, or when the user mentions ...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural terms including the .md file extension plus 'wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes', matching the anchor that calls for synonyms and file extensions.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Obsidian-only niche with distinct triggers (wikilinks, embeds, Obsidian notes) that are unlikely to fire for unrelated skills.	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: Atmosphere/atmosphere
Path: .claude/skills/obsidian-markdown/SKILL.md
Commit: 468f0ea

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