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

89%

Does it follow best practices?

Impact

100%

1.19x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

79%

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

This is a well-structured, concise skill that effectively teaches Obsidian-specific Markdown syntax through concrete examples. Its main strengths are token efficiency (explicitly scoping out standard Markdown) and actionability (every feature has copy-paste syntax). Weaknesses include a somewhat superficial workflow with a non-actionable verification step and missing bundle reference files that the skill points to.

Suggestions

Replace the vague 'Verify the note renders correctly' step with actionable validation Claude can perform, such as checking frontmatter YAML validity, ensuring wikilinks use correct syntax, and confirming block IDs follow naming rules.

Provide the referenced bundle files (references/PROPERTIES.md, references/EMBEDS.md, references/CALLOUTS.md) or remove the references if they don't exist.

Dimension	Reasoning	Score
Conciseness	The skill explicitly states it covers only Obsidian-specific extensions and assumes standard Markdown knowledge. Every section is lean with syntax examples rather than explanations. No unnecessary padding or concept explanations.	3 / 3
Actionability	Every feature is demonstrated with concrete, copy-paste-ready Markdown syntax examples. The complete example at the end shows a full working note. All syntax patterns are specific and executable.	3 / 3
Workflow Clarity	The workflow section provides a clear 6-step sequence for creating a note, but the verification step ('Verify the note renders correctly in Obsidian's reading view') is vague and not actionable by Claude since it can't open Obsidian. There's no validation feedback loop for common errors like malformed frontmatter or broken wikilinks.	2 / 3
Progressive Disclosure	The skill references PROPERTIES.md, EMBEDS.md, and CALLOUTS.md in a references/ directory with clear signaling, which is good structure. However, no bundle files were provided, so these references are broken. The inline content is well-organized but some sections (Math, Mermaid, Footnotes) could arguably be in reference files to keep the main skill leaner.	2 / 3
	Total	10 / 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.

This is an excellent skill description that hits all the marks. It uses third person voice, lists specific capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, and carves out a clear niche that distinguishes it from general Markdown or note-taking skills. It closely matches the style and quality of the good examples in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and features: 'Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.' This names the domain clearly and enumerates specific capabilities.	3 / 3
Completeness	Clearly answers both 'what' (create and edit Obsidian Flavored Markdown with specific syntax features) and 'when' (explicit 'Use when...' clause listing file types and trigger terms like wikilinks, callouts, frontmatter, tags, embeds, Obsidian notes).	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Obsidian', '.md files', 'wikilinks', 'callouts', 'frontmatter', 'tags', 'embeds', 'Obsidian notes'. These are all terms a user working with Obsidian would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Obsidian-specific Markdown. The triggers (wikilinks, callouts, embeds, Obsidian notes) are specific enough to distinguish this from a general Markdown skill or other document editing skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: kepano/obsidian-skills
Commit: a1dc48e

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