obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
66
51%
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 ./openclaw/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, relying on 'work with' without specifying concrete actions. It lacks a 'Use when...' clause entirely, making it difficult for Claude to know when to select this skill. The mention of Obsidian and obsidian-cli provides some distinctiveness but is insufficient for reliable skill selection.
Suggestions
Add specific concrete actions like 'Create, search, link, and tag notes in Obsidian vaults; manage templates; query vault contents via obsidian-cli'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Obsidian, vault management, note linking, backlinks, or obsidian-cli commands'.
Include more natural trigger terms users would say, such as 'notes', 'knowledge base', 'backlinks', 'daily notes', 'tags', or 'zettelkasten'.
| 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 extremely vague ('work with' and 'automate'), and there is no 'when' clause or explicit trigger guidance at all. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings this 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-oriented terms users would naturally 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 editing skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%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 immediately actionable CLI commands and practical vault discovery guidance. Its main weaknesses are the lack of validation/verification steps after potentially destructive operations (move, delete) and the absence of references to deeper documentation or troubleshooting resources. Overall it's a strong, efficient skill that respects Claude's intelligence.
Suggestions
Add a brief validation step after move/rename operations (e.g., 'verify with `obsidian-cli search` that the note exists at the new path and spot-check a few backlinks')
Consider adding a troubleshooting note or link for when the URI handler fails or `obsidian-cli` can't find vaults
| 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 waste tokens explaining 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 independent commands rather than a sequenced workflow. The vault discovery section has a clear decision flow, but there are no validation checkpoints—e.g., after move/rename, no step to verify links were updated correctly, and no error recovery guidance for failed operations. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from vault structure to discovery to CLI commands. However, for a skill of this scope, some content (like the full CLI command reference) could benefit from being split into a separate reference file, and there are no references to external docs or deeper materials. | 2 / 3 |
Total | 10 / 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
- trpc-group/trpc-agent-go
- Commit
af8bd5f
- 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.