A tight, highly actionable skill body: every section is a concrete command table, safety guidance is explicit, and error-recovery for the disabled-CLI case is included. The only refinements are a couple of unexplained bare commands and a couple of implicit verification checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no concept padding; the single orienting line ("An Obsidian vault is a normal folder of Markdown files plus `.obsidian/` config") conveys operational facts rather than explaining what Claude already knows. Every section and code block earns its place, matching anchor 5.	5 / 5
Actionability	Concrete copy-paste-ready CLI commands throughout (e.g., `obsidian search query="OpenClaw" format=json`, `obsidian backlinks path="Folder/Note.md"`), with smart fallback guidance (apply_patch for multi-line content). Minor gaps keep it at anchor 4 rather than 5: bare unexplained commands like `obsidian daily:path` and `obsidian daily:read`, and placeholder paths with no worked example of real output.	4 / 5
Workflow Clarity	Clear sequence (First Checks → Read → Write → Bases/Canvas → Safety) with an explicit error-recovery loop for the disabled-CLI case and validation guidance ("validate JSON after edits", "Use targeted paths and review diffs"), satisfying the destructive-operation checkpoint requirement. Anchor 4 rather than 5 because some checkpoints remain implicit, e.g., no explicit verify step that links were updated after `obsidian move`.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single well-organized document with clear section headers and no nested or buried references. Anchor 4 fits: structure is good and content is appropriately inline for a single-file skill, though a CLI reference of this size (three large command blocks plus command lists) could arguably be split into a one-level-deep reference file.	4 / 5
	Total	17 / 20 Passed

Description

70%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 concise, distinctive, domain-specific description with concrete named capabilities, but it is missing the "when" half entirely — no trigger guidance telling Claude when to reach for it. Adding a "Use when..." clause with natural trigger phrases would resolve its main weakness.

Suggestions

Add an explicit trigger clause, e.g. "Use when working with an Obsidian vault, or when the user mentions notes, backlinks, wikilinks, daily notes, Canvas, or Bases files."

Add natural synonyms and file extensions users would say (e.g., "markdown notes", "wikilinks", ".canvas", ".base") to broaden trigger-term coverage.

Attach verbs to the remaining nouns (e.g., "traverse backlinks", "query Bases") so every listed capability reads as a concrete action.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("search/read/write notes, backlinks, Bases, Canvas") in a terse domain-specific form, but lacks verbs for backlinks/Bases/Canvas and omits capabilities like daily notes, links, and outline work. Anchor 4 (several specific actions, minor gaps) fits better than 5 (not comprehensive) or 3 (more than 1-2 actions named).	4 / 5
Completeness	The "what" is clear (search/read/write notes, backlinks, Bases, Canvas), but there is no "when" clause at all — no "Use when..." or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 4 because "when" is entirely absent, not merely less explicit.	3 / 5
Trigger Term Quality	"Obsidian vault", "notes", "backlinks", "Bases", "Canvas" are natural terms users would say, giving good keyword coverage. A few natural terms are missing (e.g., "daily notes", "wikilinks", "markdown notes"), matching anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	"Obsidian vault" carves out a clear niche with distinct triggers (backlinks, Bases, Canvas are Obsidian-specific), so conflict risk with other skills is minimal. This matches anchor 5; no neighboring anchor fits better.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: steipete/agent-scripts
Path: skills/obsidian/SKILL.md
Commit: 79150cf

Reviewed: 2 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.