CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

88

1.06x
Quality

83%

Does it follow best practices?

Impact

100%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A solid, example-driven reference for Obsidian Flavored Markdown with good structure and an authoritative complete example. Its main weakness is conciseness: it teaches generic markdown basics Claude already knows, which inflates the body without adding skill-specific value.

Suggestions

Trim the Basic Formatting, Lists, Code Blocks, and Tables sections to Obsidian-specific deviations only, since Claude already knows standard markdown syntax.

Keep the callouts, wikilinks, embeds, properties, and tags sections — these are the genuinely Obsidian-specific constructs that earn their tokens.

Consider moving the large Callout Types and Property Types reference tables into a separate reference file to slim the inline body.

DimensionReasoningScore

Conciseness

The body is mostly efficient syntax tables and code blocks, but ~450 lines cataloging basic markdown (headings, bold/italic, lists, tables) that Claude already knows adds padding the skill could trim.

3 / 5

Actionability

Concrete copy-paste-ready syntax examples for every Obsidian construct, plus a fully worked complete example; minor gaps are in edge cases rather than core usage.

4 / 5

Workflow Clarity

Each feature is clearly demonstrated with grouped examples and a synthesizing complete example, but there are no validation checkpoints — acceptable because editing markdown is non-destructive, so the cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a dedicated external References list; the content is inline rather than split into bundle files, but no bundle files exist and the sectioning keeps it navigable.

4 / 5

Total

15

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, natural trigger terms, explicit what-and-when guidance, and a distinct Obsidian niche. It reads in third person and is concise rather than padded.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('wikilinks, embeds, callouts, properties') tied to a named domain, giving comprehensive coverage of the syntax the skill manipulates.

5 / 5

Completeness

Explicitly answers both 'what' (create/edit Obsidian Flavored Markdown with the listed features) and 'when' ('Use when working with .md files in Obsidian, or when the user mentions...'), matching the anchor's two-part trigger pattern.

5 / 5

Trigger Term Quality

Covers natural terms users would say ('wikilinks, callouts, frontmatter, tags, embeds, Obsidian notes') plus file extension cues ('.md files in Obsidian'), a comprehensive and natural trigger set.

5 / 5

Distinctiveness Conflict Risk

The Obsidian-specific trigger surface (wikilinks, callouts, embeds, Obsidian vault) carves a clear niche unlikely to fire for unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.