obsidian-cli

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

Quality

90%

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

88%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 well-crafted skill body: concrete executable commands, a clear when-to/when-not-to frame, and a plugin develop/test cycle with real validation feedback loops. Its main structural weakness is that all guidance — including the lengthy Common Mistakes section — lives inline in SKILL.md with no internal reference files.

Dimension	Reasoning	Score
Conciseness	The body is efficient and skill-specific throughout (the Mindset section explains CLI architecture, not concepts Claude already knows), but the WHY paragraphs in Common Mistakes partially restate their NEVER rules and could be tightened slightly. It is above the 3 anchor because no section is padded or teaches known material.	4 / 5
Actionability	The "Common patterns" block provides copy-paste-ready commands covering the common cases, and every section (syntax, targeting, plugin dev) gives fully executable examples like `obsidian search query="search term" limit=10` and `obsidian dev:errors`.	5 / 5
Workflow Clarity	The develop/test cycle is a numbered 1-4 sequence with explicit validation checkpoints (error check, screenshot/DOM verification, console output) and a genuine feedback loop — "if errors appear, fix and repeat from step 1" — matching the 5 anchor's error-recovery loop.	5 / 5
Progressive Disclosure	Section structure is good and the full command reference is appropriately deferred to `obsidian help` and a clearly signaled one-level-deep external link. It falls short of 5 because no bundle files exist and the ~70-line Common Mistakes section is entirely inline rather than split out.	4 / 5
	Total	18 / 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.

A strong description that clearly states capabilities in third-person imperative voice and pairs them with an explicit, concrete "Use when..." clause covering both vault operations and plugin development. The only gap is minor: a few natural trigger synonyms (daily notes, backlinks, obsidian.md) are absent.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions across both domains — "read, create, search, and manage notes, tasks, properties" and "reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM" — giving comprehensive coverage rather than the minor gaps of a 4.	5 / 5
Completeness	It explicitly answers both questions: a detailed "what" (concrete read/create/search/manage and plugin-dev actions) and a concrete "Use when..." trigger clause enumerating five distinct use scenarios, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	Natural phrases like "interact with their Obsidian vault", "manage notes", "search vault content", and "develop and debug Obsidian plugins" are present, but a few common user variations (e.g. "daily notes", "backlinks", "obsidian.md") are missing, keeping it just below the comprehensive synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear niche — the Obsidian CLI specifically — and every trigger phrase names Obsidian explicitly, so it is unlikely to fire for unrelated note-taking or plugin skills.	5 / 5
	Total	19 / 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: pantheon-org/tekhne
Path: skills/documentation/obsidian/obsidian-cli/SKILL.md
Commit: a1083f4

Reviewed: 4 hours 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.