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 describe concrete actions or provide any trigger guidance for when Claude should select this skill. It reads more like a topic label than a functional description, leaving Claude unable to confidently choose it over other markdown or note-related skills.
Suggestions
Add specific concrete actions like 'Create, search, link, and organize notes in Obsidian vaults; manage tags, backlinks, and metadata; run obsidian-cli commands for bulk operations'.
Add an explicit 'Use when...' clause such as 'Use when the user mentions Obsidian, vault management, knowledge base notes, backlinks, or obsidian-cli commands'.
Include natural trigger terms users would say: 'notes', 'knowledge base', 'backlinks', 'tags', 'daily notes', '.md files', 'second brain'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'work with' which is vague, and 'automate via obsidian-cli' names a tool but doesn't describe concrete actions like creating notes, linking pages, searching vaults, or managing tags. | 1 / 3 |
Completeness | The 'what' is extremely vague ('work with' and 'automate') and there is no 'when' clause or explicit trigger guidance at all, which per the rubric caps completeness at 2 maximum, and 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' 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 |
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 work with Obsidian vaults and obsidian-cli. Its strengths are excellent conciseness and actionability with specific commands and file paths. The main weakness is the lack of validation/verification steps after potentially impactful operations like move/rename (which modifies links across the vault).
Suggestions
Add a brief validation step after `obsidian-cli move` to verify wikilinks were updated correctly (e.g., grep for old references), since this is a vault-wide refactoring operation.
| 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 rather than 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. | 3 / 3 |
Workflow Clarity | The skill covers multiple operations but presents them as a reference list rather than a sequenced workflow. For vault discovery there's a clear two-step decision (check default, then fall back to config), which is good. However, there are no validation checkpoints—e.g., after move/rename, no step to verify links were updated correctly; after create, no verification the note exists. For a tool that modifies vault-wide links, a validation step would be valuable. | 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 sub-operations). 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.