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.
96
93%
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 follows best practices closely. It uses third person voice, lists specific concrete capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, and occupies a clearly distinct niche. It closely mirrors the good examples provided 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 — targets Obsidian-specific markdown syntax which is a clear niche. The mention of wikilinks, callouts, embeds, and Obsidian-specific features distinguishes it from generic markdown editing skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 teaches Obsidian-specific Markdown syntax with concrete examples and good progressive disclosure to reference files. Its main weakness is the workflow section, where the verification step is not actionable for Claude and lacks a concrete validation mechanism. Overall, it's a strong reference skill that respects token budget while being highly actionable.
Suggestions
Replace the vague 'Verify the note renders correctly' step with something Claude can actually do, such as checking for common syntax errors (unclosed callouts, malformed frontmatter YAML, unmatched `%%` comments) or providing a validation checklist.
| 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 and no unnecessary explanation of concepts Claude already knows. | 3 / 3 |
Actionability | All syntax is shown with concrete, copy-paste-ready Markdown examples. The complete example at the end demonstrates a full note with multiple features combined. Every section provides executable syntax patterns rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The workflow section lists clear steps for creating an Obsidian note, but the verification step ('Verify the note renders correctly in Obsidian's reading view') is vague and not actionable by Claude, since Claude cannot open Obsidian. There's no feedback loop or concrete validation mechanism for catching syntax errors. | 2 / 3 |
Progressive Disclosure | The skill provides a concise overview with well-signaled one-level-deep references to PROPERTIES.md, EMBEDS.md, and CALLOUTS.md for detailed information. Content is appropriately split between the main file and reference files, with clear navigation links. | 3 / 3 |
Total | 11 / 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
fa1e131
- 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.