obsidian

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

2.12x

Quality

55%

Does it follow best practices?

Impact

100%

2.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/obsidian/SKILL.md

Quality

Content

87%

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

This is a well-crafted, concise skill that efficiently teaches Claude how to interact with Obsidian vaults and use obsidian-cli. Its main strength is actionability—every command is concrete and ready to use, with practical warnings about edge cases. The main weakness is the lack of validation steps for potentially destructive operations like move/rename and delete, which prevents workflow clarity from scoring higher.

Suggestions

Add a verification step after move/rename operations, e.g., 'After moving, grep for old path to confirm all links were updated'

Add a brief validation note for delete operations, such as confirming the note exists before deletion or checking for incoming links that would break

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It assumes Claude knows what Markdown is, what Obsidian is at a high level, and doesn't over-explain basic concepts. Every section delivers actionable information without padding.	3 / 3
Actionability	Provides specific, copy-paste-ready CLI commands for every operation (search, create, move, delete, set-default). Includes concrete file paths for vault discovery and practical notes about edge cases (dot-folders, URI handler requirement).	3 / 3
Workflow Clarity	The skill covers multiple operations but presents them as a reference list rather than a sequenced workflow. The vault discovery section has a clear decision flow, but there are no validation checkpoints—e.g., no guidance on verifying that a move/rename correctly updated all wikilinks, or confirming a create succeeded.	2 / 3
Progressive Disclosure	For a skill of this size (~50 lines) with no bundle files, the content is well-organized into logical sections (vault structure, finding vaults, CLI quick start) with clear headers. No external references are needed given the scope, and the content isn't monolithic.	3 / 3
	Total	11 / 12 Passed

Description

22%

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 identifies the domain (Obsidian vaults) and a tool (obsidian-cli) but fails to specify concrete actions and lacks any 'Use when...' trigger guidance. It is too vague to help Claude reliably select this skill from a large pool, and the phrase 'work with' provides almost no actionable information about capabilities.

Suggestions

Add specific concrete actions such as 'Create, search, link, and organize notes in Obsidian vaults; manage tags, backlinks, and metadata via obsidian-cli'.

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Obsidian, vault management, knowledge base notes, or obsidian-cli commands'.

Include natural trigger terms users would say, such as 'notes', 'knowledge base', 'backlinks', 'tags', 'daily notes', '.md files'.

Dimension	Reasoning	Score
Specificity	The description says 'work with' which is vague, and 'automate via obsidian-cli' names a tool but doesn't specify concrete actions like creating notes, linking, searching, or managing tags.	1 / 3
Completeness	The 'what' is vague ('work with' and 'automate') and there is no 'when' clause or explicit trigger guidance, which per the rubric should cap completeness at 2 at most, but the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	Includes 'Obsidian', 'vaults', 'Markdown notes', and 'obsidian-cli' which are relevant keywords, but misses common user terms like 'notes', 'knowledge base', 'backlinks', 'tags', or '.md files'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Obsidian vaults' and 'obsidian-cli' provides some distinctiveness from generic markdown or note-taking skills, but 'plain Markdown notes' could overlap with general markdown editing skills.	2 / 3
	Total	6 / 12 Passed

Validation

72%

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 — 8 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: deepgram/dglabs-deepclaw
Commit: ec8d4f8

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