Tessl • The package manager for agent skills

SkillPublic

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.

1.06x

Quality

82%

Does it follow best practices?

Impact

100%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

70%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.

The Obsidian-specific material (wikilinks, embeds, callouts, properties, tags, comments) is excellent — concrete, correct, and immediately usable — but it is buried in a monolithic file that also re-explains generic Markdown Claude already knows, roughly doubling the token cost. Splitting Obsidian-specific detail into reference files and cutting the standard-Markdown sections would lift both weak dimensions.

Suggestions

Delete the sections covering standard CommonMark (Headings, Text Styling, Lists, Code Blocks, Tables, Math, Footnotes) — Claude already knows these; keep only Obsidian's divergences from standard Markdown (e.g., ==highlight==, %%comments%%, bare-URL behavior).

Move the callout-type table and the multi-section Complete Example into a references/ file (e.g., references/callouts.md, references/example-note.md) and link them from SKILL.md so the main file is a lean syntax overview.

Fold the block-reference, embed-size, and PDF-embed sub-sections into a single compact 'Obsidian-specific syntax' cheat-sheet table to cut remaining duplication between the section examples and the Complete Example.

Dimension	Reasoning	Score
Conciseness	Roughly half the ~445-line body re-teaches standard CommonMark Claude already knows — sections on headings, bold/italic/strikethrough, unordered/ordered lists, tables, fenced code blocks, inline code, LaTeX math, and footnotes are not Obsidian-specific. The examples are terse code blocks rather than padded prose, which keeps it above a 1, but the volume of redundant sections is noticeably more than 'some unnecessary explanation'.	2 / 5
Actionability	Every Obsidian-specific construct ships as copy-paste-ready syntax ("[[Note Name#^block-id]]", "![[image.png\|400x300]]", "> [!note]- Collapsed by default", "![[document.pdf#page=5]]", the YAML properties block) and a complete worked example note demonstrates them together — fully executable reference material covering the common cases.	5 / 5
Workflow Clarity	This is a single-purpose, non-destructive syntax-reference skill: the one action (emit valid Obsidian Flavored Markdown) is unambiguous and fully specified, so the simple-skill exception applies and no multi-step workflow or validation checkpoint is needed.	5 / 5
Progressive Disclosure	No bundle files exist and all content lives inline in SKILL.md with clear section headers — decent structure, but the 13-row callout-type table and the 70-line 'Complete Example' are exactly the content that belongs in separate reference files, matching the anchor where content that should be separate is inline. The <50-line simple-skill exception does not apply to a ~445-line file.	3 / 5
	Total	15 / 20 Passed

Description

87%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: third-person voice, concrete capability list, and an explicit 'Use when…' clause with natural trigger terms covering the Obsidian niche. The only gaps are a couple of missing synonyms (vault, backlinks, internal links) and a slightly thin action-verb list in the 'what' clause.

Dimension	Reasoning	Score
Specificity	"Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties" names the domain and enumerates several specific capabilities, but relies on only two action verbs and defers breadth to "other Obsidian-specific syntax" rather than listing concrete actions like tag creation or block references — several specific actions with minor gaps, not fully comprehensive.	4 / 5
Completeness	It explicitly 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") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Triggers include natural phrases users would say — "wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes" plus ".md files in Obsidian" — but miss common synonyms like "vault", "backlinks", or "internal links", so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	"Obsidian" and its unique syntax terms (wikilinks, callouts, embeds) form a clear niche with distinct triggers; it would not plausibly fire for a generic Markdown or document skill, so conflict risk is minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/obsidian-markdown/SKILL.md
Revision: 868d035

Reviewed: 22 days ago

Discovery Implementation Validation

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.

obsidian-markdown

Table of Contents

Is this your skill?