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.
Install with Tessl CLI
npx tessl i github:kepano/obsidian-skills --skill obsidian-markdown95
Does it follow best practices?
Validation 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 follows best practices. It uses third person voice, lists specific capabilities, includes a comprehensive 'Use when...' clause with natural trigger terms, and clearly distinguishes itself from generic Markdown or document skills. The description provides sufficient detail for Claude to confidently select this skill when users work with Obsidian-specific features.
| 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 (Obsidian Markdown) and specific features (wikilinks, embeds, callouts, properties). | 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.' These are the exact terms Obsidian users naturally use when discussing their notes. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers specific to Obsidian ecosystem. The mention of 'Obsidian Flavored Markdown,' 'wikilinks,' 'callouts,' and 'Obsidian notes' clearly distinguishes this from generic Markdown skills or other note-taking tools. | 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-crafted skill that efficiently covers Obsidian-specific Markdown extensions with concrete, executable examples. The progressive disclosure is excellent with clear references to detailed documentation. The main weakness is the workflow's validation step, which could be more specific about what to check and how to handle rendering issues.
Suggestions
Expand the verification step with specific checks: 'Verify wikilinks resolve (no broken link indicators), embeds display content, and callouts render with correct styling'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, explicitly stating it assumes standard Markdown knowledge. Every section provides only Obsidian-specific syntax without explaining concepts Claude already knows. | 3 / 3 |
Actionability | All syntax examples are concrete, copy-paste ready code blocks with clear annotations. The complete example at the end demonstrates real-world usage combining multiple features. | 3 / 3 |
Workflow Clarity | The workflow section provides a clear 6-step sequence, but the validation step ('Verify the note renders correctly') is vague and lacks specific checkpoints or error recovery guidance for common issues. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-signaled one-level-deep references to PROPERTIES.md, EMBEDS.md, and CALLOUTS.md. Content is appropriately split between quick reference and detailed documentation. | 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.
- 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.