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.
90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 provides specific capabilities (wikilinks, embeds, callouts, properties), includes natural trigger terms that Obsidian users would actually say, explicitly states when to use it with a 'Use when...' clause, and clearly distinguishes itself from generic markdown handling through Obsidian-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.' This clearly names the domain and enumerates specific features/capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties') AND when ('Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'wikilinks', 'callouts', 'frontmatter', 'tags', 'embeds', 'Obsidian notes', '.md files', and 'Obsidian'. These are the exact terms Obsidian users naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Obsidian-specific markdown syntax. The explicit mention of 'Obsidian Flavored Markdown' and Obsidian-specific features like wikilinks and callouts distinguishes it from generic markdown skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference skill with excellent actionability through concrete, executable examples for every Obsidian-specific syntax feature. However, it's overly verbose by including basic markdown concepts Claude already knows (headings, bold/italic, standard code blocks) and could benefit from splitting into multiple files for better progressive disclosure. The Obsidian-specific content (wikilinks, callouts, embeds, properties) is well-documented and immediately usable.
Suggestions
Remove basic markdown sections (headings, text styling, standard code blocks, tables) that Claude already knows - focus only on Obsidian-specific syntax
Split into multiple files: keep SKILL.md as a quick reference with links to detailed files like CALLOUTS.md, EMBEDS.md, PROPERTIES.md
Remove the 'When to Use This Skill' section as it duplicates the skill description in frontmatter
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude already knows (basic markdown headings, text styling, standard code blocks). The 'When to Use This Skill' section largely duplicates the description. Could be tightened significantly. | 2 / 3 |
Actionability | Excellent concrete examples throughout with copy-paste ready markdown syntax. Every feature is demonstrated with executable code blocks showing exact syntax, and the complete example at the end ties everything together. | 3 / 3 |
Workflow Clarity | For a reference/syntax skill, this is appropriately structured. There's no multi-step destructive process requiring validation checkpoints. The content is organized logically from basic to advanced features, which is the appropriate workflow for a syntax reference. | 3 / 3 |
Progressive Disclosure | The skill is a monolithic document (~400 lines) that could benefit from splitting into separate files (e.g., callouts.md, embeds.md, properties.md). The references section at the end is good, but inline content that could be externalized remains in the main file. | 2 / 3 |
Total | 10 / 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 | |
- 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.