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.
80
71%
Does it follow best practices?
Impact
100%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/obsidian-markdown/SKILL.mdQuality
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 hits all the marks. 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 around Obsidian-specific markdown syntax. 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 with a clear niche around Obsidian-specific markdown. The mention of Obsidian Flavored Markdown, wikilinks, callouts, and embeds clearly distinguishes this from generic markdown or other note-taking skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive and actionable Obsidian syntax examples but is severely bloated by including standard Markdown features Claude already knows (headings, bold, lists, code blocks, tables, math, mermaid). The monolithic structure with no progressive disclosure wastes context window tokens. The Obsidian-specific content (wikilinks, embeds, callouts, properties, block references, comments) is well-done but buried among unnecessary basics.
Suggestions
Remove all standard Markdown sections (Basic Formatting, Lists, Code Blocks, Tables, Math, Mermaid, Footnotes) and focus exclusively on Obsidian-specific syntax extensions that Claude wouldn't already know.
Split the content into a concise SKILL.md overview with Obsidian-specific quick reference, and move the callout types table, complete example, and HTML support into separate bundle files (e.g., CALLOUT_TYPES.md, EXAMPLE.md).
Add a brief 'Common Pitfalls' section covering YAML frontmatter validation issues (e.g., unescaped colons in titles, wikilinks in properties needing quotes) and block ID formatting constraints.
Reduce the complete example section to a minimal snippet showing only Obsidian-specific features combined, rather than a full note demonstrating standard Markdown alongside Obsidian features.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose — much of this is standard Markdown syntax (headings, bold, italic, lists, code blocks, tables, footnotes) that Claude already knows. The skill should focus only on Obsidian-specific extensions (wikilinks, embeds, callouts, properties, block references, comments). Basic formatting, ordered/unordered lists, inline code, fenced code blocks, math, and mermaid diagrams are all standard Markdown or widely known and waste significant token budget. | 1 / 3 |
Actionability | The content provides concrete, copy-paste-ready syntax examples for every feature. Each section shows exact markdown syntax with realistic examples that can be directly used in Obsidian files. | 3 / 3 |
Workflow Clarity | This is primarily a reference/syntax skill rather than a multi-step workflow, so explicit validation steps are less critical. However, there's no guidance on common pitfalls (e.g., invalid YAML frontmatter, broken wikilinks, block ID formatting constraints) or how to verify correctness of generated Obsidian markdown. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text at ~350+ lines with no bundle files to offload detail into. The callout types table, complete example, basic formatting sections, and HTML support could all be in separate reference files. Everything is inlined into a single massive document with no layered structure. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.