obsidian

Work with Obsidian vaults using the official obsidian CLI: read/search/create/edit notes, tasks, links, properties, plugins.

Quality

85%

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

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and highly actionable with executable CLI examples and clean organization. Its main weakness is the absence of validation/verification steps for destructive operations like move and delete.

Suggestions

Add a brief workflow with validation for destructive operations, e.g. verify a target path exists before `obsidian move` and confirm before `obsidian delete`.

Include a verification step after edits (e.g. re-read the note or check `obsidian dev:errors`) to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean, command-focused content with no concept padding; assumes Claude's competence and every token earns its place.	3 / 3
Actionability	Provides concrete, executable `obsidian` commands grouped by task (open, search, create, move, daily, properties) — copy-paste ready.	3 / 3
Workflow Clarity	Commands are grouped but there is no sequenced multi-step workflow with validation checkpoints; destructive ops like delete/move lack feedback loops, capping this at 2.	2 / 3
Progressive Disclosure	A compact single file with well-organized sections and no bundle files; under the simple-skill threshold where good organization scores 3.	3 / 3
	Total	11 / 12 Passed

Description

82%

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, action-oriented, and distinctive, but omits an explicit 'Use when...' trigger clause that would tell Claude when to invoke it. Adding a short usage trigger would raise completeness.

Suggestions

Append a 'Use when working with Obsidian vaults, notes, tasks, or properties' clause so the 'when' is explicit.

Mention common user phrasings like 'Obsidian notes' or 'my vault' to strengthen natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "read/search/create/edit notes, tasks, links, properties, plugins" — which matches the score-3 anchor of enumerating several specific capabilities.	3 / 3
Completeness	Clearly states what the skill does but lacks an explicit 'when to use' trigger clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms users would say ("Obsidian vaults", "notes", "tasks", "links", "properties", "plugins") are well covered; not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	"Obsidian vaults using the official obsidian CLI" defines a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenBMB/PilotDeck
Path: skills/obsidian/SKILL.md
Commit: c88d7d1

Reviewed: about 13 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.