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.
93
89%
Does it follow best practices?
Impact
100%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
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 clearly defines its scope (Obsidian Flavored Markdown), lists specific capabilities (wikilinks, embeds, callouts, properties), and provides explicit trigger guidance with natural user terms. It uses proper third-person voice and follows the recommended 'Use when...' pattern. It would be easily distinguishable from generic Markdown or other note-taking skills.
| 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 unique to Obsidian and unlikely to conflict with generic Markdown or other document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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 efficiently covers Obsidian-specific Markdown syntax with excellent concrete examples. Its main weaknesses are the unverifiable progressive disclosure references (bundle files not provided) and a workflow verification step that isn't actionable for Claude. The content is highly actionable and respects Claude's intelligence throughout.
Suggestions
Provide the referenced bundle files (references/PROPERTIES.md, references/EMBEDS.md, references/CALLOUTS.md) to fulfill the progressive disclosure promises made in the skill body.
Replace the vague 'Verify the note renders correctly' step with actionable validation Claude can perform, such as checking frontmatter YAML validity, ensuring all wikilinks use correct syntax, and confirming callout types are from the known list.
| 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 syntax feature includes concrete, copy-paste-ready Markdown examples with clear annotations. The complete example at the end demonstrates real-world usage combining multiple features. All code blocks are executable Obsidian Markdown. | 3 / 3 |
Workflow Clarity | The workflow section provides a clear 6-step sequence for creating an Obsidian note, but the verification step ('Verify the note renders correctly in Obsidian's reading view') is vague and not actionable from Claude's perspective since Claude cannot render in Obsidian. There are no feedback loops or error recovery steps for common issues like invalid frontmatter or broken wikilinks. | 2 / 3 |
Progressive Disclosure | The skill references PROPERTIES.md, EMBEDS.md, and CALLOUTS.md for detailed content, which is good structure. However, no bundle files were provided, so these references lead nowhere. The external Obsidian help links are a nice touch, but the missing bundle files undermine the progressive disclosure promise. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
ac93987
- Reviewed
Table of Contents
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.