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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%

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 Obsidian syntax reference with copy-paste examples throughout, but it is a monolithic ~600-line document that re-covers standard markdown Claude already knows and does not progressively disclose detail into separate bundle files.

Suggestions

Trim or collapse the standard-markdown sections (headings, bold/italic, lists, tables, blockquotes, code blocks, math, footnotes, HTML, Mermaid) to focus the body on Obsidian-specific syntax Claude does not already know.

Split large Obsidian feature areas (e.g. callouts, embeds, properties/frontmatter) into one-level-deep reference files under ./references/ with clearly signaled links from SKILL.md, leaving a concise overview in the main file.

Since there are no destructive or batch operations, consider adding a brief 'how to apply this syntax' note or a single canonical end-to-end example with explicit verification (e.g. confirming wikilinks resolve / frontmatter parses) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The Obsidian-specific sections are lean (code blocks with minimal prose), but large portions cover standard markdown Claude already knows (headings, bold/italic, lists, tables, code blocks, blockquotes, math, footnotes, HTML, Mermaid), so it is mostly efficient but padded with redundant reference material.	2 / 3
Actionability	Every feature is shown with concrete, copy-paste-ready syntax examples (e.g. `![[Note Name#^block-id]]`, `> [!faq]- Collapsed by default`), matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The skill is a syntax catalog with no multi-step process to sequence and no validation checkpoints; sections are well-organized but the 'Complete Example' is illustrative rather than a guided, checkpointed workflow.	2 / 3
Progressive Disclosure	No bundle files exist and the entire ~600-line reference lives inline in SKILL.md; sections are clearly headed, but content that could be split (callouts, embeds, properties) is monolithic rather than distributed across one-level-deep reference files.	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 strong: third-person voice, concrete capabilities, explicit 'Use when' triggers, and a clear Obsidian-specific niche that minimizes conflict risk. It cleanly satisfies all four dimensions at the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Create and edit') applied to specific Obsidian syntax elements (wikilinks, embeds, callouts, properties), matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.	3 / 3
Completeness	Explicitly states both what ('Create and edit Obsidian Flavored Markdown...') and when ('Use when working with .md files in Obsidian, or when the user mentions...'), with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Covers natural user terms ('.md files in Obsidian', 'wikilinks, callouts, frontmatter, tags, embeds, Obsidian notes') that a user would naturally say, satisfying the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The Obsidian-specific niche and distinctive triggers (wikilinks, callouts, embeds, Obsidian notes) make it unlikely to fire for an unrelated skill, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (621 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 2 missing, 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: heyitsnoah/claudesidian
Path: .agents/skills/obsidian-markdown/SKILL.md
Commit: 6c56f35

Reviewed: about 14 hours 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.