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, essentially saying it 'works with' Obsidian without specifying concrete capabilities or when to use it. While the mention of Obsidian and obsidian-cli provides some distinctiveness, the lack of specific actions and explicit trigger guidance makes it difficult for Claude to know when to select this skill over others.
Suggestions
List specific concrete actions such as 'Create, search, link, and organize notes in Obsidian vaults; manage tags, backlinks, and metadata; execute obsidian-cli commands'.
Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions Obsidian, vault management, note-taking with Markdown, backlinks, or obsidian-cli commands'.
Include natural trigger terms users would say, such as 'notes', 'knowledge base', 'backlinks', 'tags', 'daily notes', 'templates', and '.md files'.
| 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 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. 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
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 solid, concise skill that provides actionable CLI commands and practical guidance for working with Obsidian vaults. Its main strengths are token efficiency and concrete, executable commands. The main weaknesses are the lack of validation/verification steps for destructive operations (move/delete) and the absence of references to more detailed documentation for advanced use cases.
Suggestions
Add a brief validation step after move/delete operations (e.g., 'After move, verify links updated: `obsidian-cli search-content "old/path"` should return no results').
Consider adding a reference to obsidian-cli's full documentation or help output for advanced flags and options not covered here.
| 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 for potentially destructive operations like move/delete (e.g., verify the move updated links correctly, or confirm before delete). | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but everything is inline in a single file. For a skill of this size (~50 lines) this is borderline acceptable, but the vault structure details and CLI reference could benefit from being split or having references to obsidian-cli docs for advanced usage. | 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
0c1ec2b
- 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.