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 is too vague to be effective for skill selection. It identifies the domain (Obsidian/markdown notes) and a tool (obsidian-cli) but fails to specify concrete actions or provide any trigger guidance. It would benefit significantly from listing specific capabilities and adding explicit 'Use when...' conditions.
Suggestions
Add specific concrete actions like 'Create, search, link, and organize notes in Obsidian vaults; manage tags, backlinks, and metadata; execute obsidian-cli commands'.
Add an explicit 'Use when...' clause such as 'Use when the user mentions Obsidian, vault management, note-taking with markdown, backlinks, obsidian-cli, or .md note organization'.
Include natural trigger terms users would say, such as 'notes', 'knowledge base', 'backlinks', 'daily notes', 'templates', 'tags', and 'vault'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'work with' and 'automate via' which are vague actions. It doesn't list any concrete actions like creating notes, linking notes, searching vaults, managing tags, etc. | 1 / 3 |
Completeness | The 'what' is extremely vague ('work with' and 'automate'), and there is no 'when' clause or explicit trigger guidance at all. The missing 'Use when...' clause would cap this at 2 regardless, 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. However, it misses common user terms like 'notes', 'knowledge base', 'backlinks', 'tags', '.md files', or specific task-related terms users might say. | 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-related 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 provides actionable CLI commands and practical guidance for working with Obsidian vaults. Its main weakness is the lack of validation/verification steps after operations like move/rename or create, which would strengthen workflow clarity. The content efficiently covers vault discovery, CLI usage, and important caveats without unnecessary explanation.
Suggestions
Add a brief verification step after move/rename operations (e.g., 'Verify: grep for old note name to confirm all links updated') to improve workflow clarity.
Consider adding a quick validation step after create operations (e.g., confirming the file exists on disk or checking obsidian-cli search returns it).
| 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. There are no validation checkpoints—for example, after moving/renaming notes, there's no step to verify wikilinks were updated correctly. The 'Find the active vault' section has a logical sequence but lacks explicit error handling or fallback steps. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no bundle files and no need for external references, the content is well-organized into clear sections (vault structure, finding vaults, CLI quick start with sub-operations). The structure is easy to scan and navigate without being monolithic. | 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.