obsidian

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

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian/SKILL.md

Quality

Content

76%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 crisp, highly actionable command reference that respects token budget and needs no external bundle files. Its weaknesses are the missing validation guidance around destructive operations (delete/move) and a small amount of migration metadata that does not belong in a skill body.

Suggestions

Add a validation step before destructive commands, e.g. read the note ('obsidian read file=Note') or list matches before 'obsidian delete', and mention recovery/confirmation for batch task operations.

Remove the 'PilotDeck Migration Note' section — the temp-dir source path and review status are migration artifacts, not skill guidance.

If the command catalog grows, split full command details into a references/ file and keep SKILL.md as the overview with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	The body is a lean, example-driven command catalog that assumes competence, but the 'PilotDeck Migration Note' section (temp-dir source path, review status) is migration metadata that earns no tokens and could be trimmed.	4 / 5
Actionability	Commands are concrete, copy-paste-ready, and grouped by task (open/read, search, create/modify, move/delete, daily/tasks, properties/links, dev), covering the common cases fully.	5 / 5
Workflow Clarity	Destructive operations ('obsidian delete file=Note', 'move') and batch-style task operations appear with no validation or verification guidance, which caps workflow clarity at 3 per the guidelines despite the otherwise clear command pattern.	3 / 5
Progressive Disclosure	Sections are well organized and the inline command reference is appropriately sized for a single-file skill, but the ~70-line command catalog sits above the under-50-line exception, so structure is 'good with minor gaps' rather than top-mark.	4 / 5
	Total	16 / 20 Passed

Description

75%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 specific, well-scoped description with strong distinctiveness and good trigger keywords, undermined only by the absence of any explicit 'when to use this' guidance. Adding a Use-when clause would raise the completeness dimension to the top anchors.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions Obsidian, vaults, notes, daily notes, or .md/.canvas files.'

Include common user phrasings and extensions as trigger terms (e.g. 'markdown notes', 'backlinks', 'daily notes', '.md') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions ('read/search/create/edit notes, tasks, links, properties, plugins') covering the domain comprehensively, matching the top anchor rather than the 'minor gaps' of a 4.	5 / 5
Completeness	The 'what' is clear (work with Obsidian vaults via the CLI), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'Obsidian', 'vault', 'notes', 'tasks', and 'plugins' are present, but common variations users might say ('daily notes', 'markdown', '.md', '.canvas') are missing, fitting the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	'Obsidian vaults' plus 'the official obsidian CLI' defines a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	17 / 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
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: 66bfd09

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.