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.

16.66x

Quality

96%

Does it follow best practices?

Impact

100%

16.66x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is obsidian-cli in kepano/obsidian-skills

Quality

Content

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

An exemplary single-file CLI skill: lean, entirely executable, and free of filler. The plugin-development workflow is the highlight — a numbered reload/check/verify loop with an explicit error-recovery cycle. External reference is delegated cleanly to `obsidian help` and the always-current docs URL, which is appropriate progressive disclosure for a self-documenting CLI.

Dimension	Reasoning	Score
Conciseness	The body is lean and teaches only CLI-specific knowledge Claude cannot infer (parameter `=` syntax, wikilink-style `file=` resolution, `vault=` as first parameter, `\n`/`\t` escapes) with no concept explanations or padding; the only near-redundancy is a second mention of `obsidian help` for dev commands, which still adds new information, so it fits the 5 anchor rather than the 4.	5 / 5
Actionability	Every example is a copy-paste-ready executable command (e.g. `obsidian create name="My Note" silent overwrite`, `obsidian dev:dom selector=".workspace-leaf" text`), and the common-patterns block covers the standard use cases, matching the fully-executable top anchor.	5 / 5
Workflow Clarity	The plugin develop/test cycle is a numbered sequence with explicit validation checkpoints and a feedback loop — "if errors appear, fix and repeat from step 1" plus visual verification and a console check — matching the top anchor for sequences with explicit validation and error-recovery loops.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed: the skill self-documents via `obsidian help` ("always up to date") and the official docs URL, and the body is organized into clear, navigable sections (Syntax, File targeting, Vault targeting, Common patterns, Plugin development), which fits the well-organized single-file exception rather than the 4 anchor's organization gaps.	5 / 5
	Total	20 / 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: concrete, third-person capability listing plus an explicit trigger clause that covers both end-user vault operations and developer workflows. The only weakness is keyword coverage — no file extensions or common synonyms like "markdown notes" or "daily notes" appear.

Suggestions

Add file-extension and synonym triggers (e.g. ".md files", "markdown notes", "daily notes") to the trigger clause to lift keyword coverage to the top anchor.

Trim the hedge "and more" in the capability sentence — a closed list of concrete actions reads as more specific and matches the strongest example descriptions.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions across both vault operations ("read, create, search, and manage notes, tasks, properties") and plugin development ("reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM"), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	It clearly answers "what" with two sentences of concrete capabilities and "when" with an explicit "Use when the user asks to..." clause listing concrete triggers, exactly matching the top anchor; the 4 anchor would require a less explicit "when".	5 / 5
Trigger Term Quality	Natural user phrases like "interact with their Obsidian vault", "manage notes", "search vault content", and "develop and debug Obsidian plugins and themes" are well covered, but the description omits synonyms and file extensions (e.g. ".md", "markdown notes", "daily notes"), which the 5 anchor explicitly requires.	4 / 5
Distinctiveness Conflict Risk	Obsidian vault management is a clear niche with distinct, unambiguous triggers (vault interaction, command-line vault operations, Obsidian plugin/theme development), so conflict risk with other skills is minimal.	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: Atmosphere/atmosphere
Path: .claude/skills/obsidian-cli/SKILL.md
Commit: 1c968d5

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.