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.
76
63%
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 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
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an exhaustive Obsidian Markdown reference that includes far too much standard Markdown syntax Claude already knows, making it extremely token-inefficient. While the Obsidian-specific syntax examples (wikilinks, embeds, callouts, properties, block references, comments) are concrete and useful, they're buried in a monolithic document alongside basic formatting that adds no value. The skill lacks workflow guidance, validation steps, and progressive disclosure.
Suggestions
Remove all standard Markdown sections (headings, bold/italic, lists, ordered lists, task lists, inline code, fenced code blocks, tables, footnotes, math, mermaid) — Claude already knows these. Focus only on Obsidian-specific syntax.
Add a brief workflow section explaining how to approach creating/editing Obsidian notes (e.g., 'Always start with frontmatter properties, use wikilinks not standard markdown links, validate that block IDs are unique').
Split the detailed callout types table and property types table into a separate REFERENCE.md file, keeping only the most common examples inline.
Add edge case guidance: escaping wikilinks with \[\[, handling special characters in note names, pipe characters in wikilink display text within tables.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose — most of this content (headings, bold/italic, lists, ordered lists, task lists, inline code, fenced code blocks, tables, footnotes, math, mermaid diagrams) is standard Markdown that Claude already knows. The skill explains basic formatting concepts at length rather than focusing only on Obsidian-specific syntax (wikilinks, embeds, callouts, properties, block references, comments). The 'Supported Languages' list and basic formatting sections are pure padding. | 1 / 3 |
Actionability | The syntax examples are concrete and copy-paste ready, which is good. However, the skill is a reference document rather than actionable guidance — it shows syntax but doesn't instruct Claude on how to decide which features to use, how to handle edge cases (e.g., escaping wikilinks, special characters in note names), or how to validate output. It's more of a cheat sheet than an executable skill. | 2 / 3 |
Workflow Clarity | There is no multi-step workflow defined. The skill is a flat reference of syntax features with no sequencing, no validation steps, and no guidance on how to approach creating or editing an Obsidian note (e.g., 'start with frontmatter, then structure headings, then add links'). The complete example at the end partially compensates but lacks explicit process steps. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text at ~300+ lines with no content split into separate files. The basic Markdown formatting (which shouldn't be here at all) bloats the main file. The references section links to external Obsidian docs but there's no internal progressive disclosure — everything from basic paragraphs to advanced embeds is dumped into one file. | 1 / 3 |
Total | 6 / 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
7cc63f3
- 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.