wiki-cli

Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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 body is lean, executable, and well-structured with explicit safety validation and a single clean external reference. Its weakest dimension is workflow_clarity, where the process is thematic rather than a numbered sequence with an explicit error-recovery loop.

Suggestions

Present the detect→read/search→fallback flow as a short numbered sequence so the ordering and the 'if CLI not ready, fall back to filesystem + rg' recovery loop is explicit rather than implied.

Add an explicit validate→fix→retry step for the transport snapshot case (e.g. re-run --peek after --force to confirm available.cli.usable became true) to lift workflow_clarity to 5.

Verify the ../wiki/references/operation-transactions.md link resolves, since the reference is relied upon for the mutation-boundary guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — e.g. 'Trust `available.cli.usable`, not merely `present` or exit status' — with no padding about what Obsidian is or how CLIs work; the one explanatory sentence about why a supported CLI can be unavailable earns its place as actionable rationale, matching the 5 anchor.	5 / 5
Actionability	Concrete executable commands are given throughout — `bash "$DETECT_TRANSPORT" --peek --vault "$VAULT"`, `(cd "$VAULT" && obsidian read path="$NOTE")`, `obsidian search query="$QUERY"` — covering the common detect/read/search cases copy-paste ready with variable substitution, matching the 5 anchor.	5 / 5
Workflow Clarity	Validation checkpoints are explicit (trust `available.cli.usable`, reject absolute/traversal/symlink paths) and a Checkpoint section plus filesystem/`rg` fallback give recovery, but the flow is organized by concern rather than as a numbered sequence with a spelled-out validate→fix→retry loop, so it fits 4 rather than 5.	4 / 5
Progressive Disclosure	A concise, well-sectioned overview (Detect safely / Read and search / Mutation boundary / Checkpoint) with a single clearly signaled one-level-deep reference ([operation transactions](../wiki/references/operation-transactions.md)) and no inlined content that belongs in a separate file, matching the 5 anchor; no bundle files exist to misplace.	5 / 5
	Total	19 / 20 Passed

Description

90%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 with an explicit 'use for' trigger clause, broad natural keyword coverage with synonyms, and a clearly distinct Obsidian-CLI-read niche. The only soft spot is specificity, which states a composite action rather than enumerating several discrete capabilities.

Dimension	Reasoning	Score
Specificity	Quotes 'Detect and use the official Obsidian command-line interface for read-only vault access' plus the mutation-boundary statement — it names the domain with 1-2 concrete actions (detect transport, read-only access) but does not enumerate several specific actions, so it sits at the anchor rather than 4.	3 / 5
Completeness	It explicitly states what ('Detect and use the official Obsidian command-line interface for read-only vault access') and when via an explicit 'use for ...' trigger clause with concrete trigger phrases, satisfying the 5 anchor; the explicit trigger guidance means the missing-'use when' cap does not apply.	5 / 5
Trigger Term Quality	The clause 'use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line' gives comprehensive natural-term coverage with synonyms (Obsidian CLI / Obsidian command line / wiki-cli), matching the 5 anchor rather than 4 where terms would be missing.	5 / 5
Distinctiveness Conflict Risk	The Obsidian CLI read-transport niche with distinct triggers (vault transport, transport detection, Obsidian CLI) is clearly scoped and unlikely to fire for unrelated skills, matching the 5 anchor for a clear niche with minimal conflict risk.	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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/wiki-cli/SKILL.md
Commit: ad67087

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