obsidian-markdown

Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

71%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 content is mostly efficient and actionable with a clearly sequenced, validation-included edit workflow, but it leans on placeholder variables and depends on external reference files that are absent from the bundle. Tightening the preamble and shipping the referenced transaction/provenance docs would lift the weaker dimensions.

Suggestions

Tighten the PRODUCT_ROOT resolution preamble and transaction paragraph to reduce token weight for a fallback skill.

Replace or resolve the placeholder variables ($BUNDLE, $VAULT, $APPROVAL_SHA256) with concrete, copy-paste-ready examples or document their expected values inline.

Include the referenced operation-transactions.md and provenance.md in the skill bundle (e.g. under references/) so the core edit workflow is self-contained.

Dimension	Reasoning	Score
Conciseness	The body is largely lean with code-first examples and no padding about what Obsidian/Markdown is, but the PRODUCT_ROOT resolution preamble and transaction sequencing paragraph are slightly heavier than needed for a syntax fallback; minor trimming possible, so efficient rather than maximally lean.	4 / 5
Actionability	Provides concrete executable bash and fenced syntax examples for properties, wikilinks, callouts, and math, but core commands rely on unresolved placeholders ($BUNDLE, $VAULT, $APPROVAL_SHA256, /absolute/path/to/...), which are templated rather than copy-paste ready, a minor gap.	4 / 5
Workflow Clarity	The vault-edit workflow is clearly sequenced (draft -> read operation-transactions.md -> build bundle -> inspect -> set APPROVAL_SHA256 -> apply) with an explicit validation checkpoint via `transaction inspect`, but no explicit inspect-fails/fix/retry feedback loop is spelled out, leaving a minor validation gap rather than full error-recovery.	4 / 5
Progressive Disclosure	Sections are well-organized with one-level-deep signaled links (operation-transactions.md, provenance.md), but the skill is ~140 lines and depends on external referenced files that are not present in the skill bundle (no references/ directory and the wiki/*.md paths resolve nowhere), so references are signaled yet unavailable for core workflow detail.	3 / 5
	Total	15 / 20 Passed

Description

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

The description is specific, well-triggered, and clearly scoped to the Obsidian niche with an explicit use-when clause and an exclusion that reduces conflict risk. The only minor gap is the absence of file-extension synonyms in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ("Explain, draft, or validate") plus a comprehensive enumerated feature set ("properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid"), matching the comprehensive-coverage anchor; not 4 because there are no meaningful coverage gaps.	5 / 5
Completeness	Explicitly states both the "what" (explain/draft/validate the enumerated syntax) and a concrete "when" ("Use when the user explicitly requests Obsidian note formatting or syntax help"), matching the 5 anchor; not 4 because the when-clause is specific, not weakly implied.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ("Obsidian Flavored Markdown", "Obsidian note formatting", "syntax help", plus feature terms like wikilinks/callouts/Mermaid), but lacks file-extension style synonyms (e.g. .md) seen in the 5 anchor, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Obsidian Flavored Markdown niche is sharply bounded by the exclusion ("not for general Markdown or broad vault operations"), giving it a clear niche with minimal conflict risk per the 5 anchor.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/obsidian-markdown/SKILL.md
Commit: 32ac5a0

Reviewed: 7 days ago

Table of Contents

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.