obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
68
55%
Does it follow best practices?
Impact
100%
2.12xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/obsidian/SKILL.mdQuality
Discovery
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 specific tool (obsidian-cli) but fails to list concrete actions or provide explicit trigger guidance. It is too vague to help Claude confidently select this skill over others, and the lack of a 'Use when...' clause is a significant gap.
Suggestions
List specific concrete actions such as 'create notes, manage backlinks, search vault content, organize tags, generate daily notes'.
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user asks about Obsidian, note-taking in markdown, vault organization, backlinks, or daily notes'.
Include common user-facing terms and file extensions like 'notes', 'knowledge base', '.md files', 'tags', 'links' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'work with' and 'automate via obsidian-cli' but doesn't list any concrete actions like creating notes, linking notes, searching, tagging, or managing templates. 'Work with' is vague. | 1 / 3 |
Completeness | The 'what' is vague ('work with' and 'automate') and there is no 'when' clause or explicit trigger guidance at all. The missing 'Use when...' clause caps this at 2 per the rubric, but the 'what' is also weak, so it scores 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', 'daily notes', 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 any markdown editing skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
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 strengths are excellent conciseness and actionability with specific commands and paths. The main weakness is the lack of validation/verification steps for operations like move/rename that affect multiple files across a vault.
Suggestions
Add a verification step after `obsidian-cli move` (e.g., search for broken links or confirm the move succeeded) to improve workflow safety for refactoring operations.
Consider adding a brief error-handling note for when `obsidian-cli` commands fail (e.g., vault not found, Obsidian not running for URI-based operations).
| 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. Every section delivers actionable information without padding. The brief notes (e.g., 'Multiple vaults common... Don't guess; read config') are genuinely useful constraints, not filler. | 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 tips like avoiding dot-folders. The guidance is directly executable rather than abstract. | 3 / 3 |
Workflow Clarity | The skill covers multiple operations but presents them as independent commands rather than a sequenced workflow. For the move/rename operation (which is a refactoring action affecting links across a vault), there's no validation step to confirm links were updated correctly. The vault discovery flow is reasonably clear with its if/otherwise structure, but overall lacks explicit checkpoints. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no bundle files, the content is well-organized into logical sections (vault structure, finding vaults, CLI quick start with sub-categories). There's no need for external references given the scope, and the sections are clearly delineated and easy to navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%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
Table of Contents
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.