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 ./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 asks about Obsidian, note-taking in markdown, managing a knowledge base, or references obsidian-cli commands'.
Include natural trigger terms users would say, such as 'notes', 'knowledge base', 'backlinks', 'daily notes', 'templates', 'vault', '.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. It could be improved by adding verification steps after destructive operations (move/delete) and slightly better workflow sequencing for common multi-step tasks like vault discovery → set default → perform operations.
Suggestions
Add a verification/validation step after move and delete operations (e.g., 'confirm the note exists at the new path' or 'verify wikilinks updated correctly') to improve workflow safety.
Consider adding a brief sequential workflow example for a common end-to-end task, such as discovering a vault, setting it as default, and then performing operations on 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 waste tokens explaining basics. 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 individual commands clearly but lacks explicit workflow sequencing for multi-step operations. For example, the vault discovery process could benefit from a clearer decision tree, and there's no validation/verification step after create, move, or delete operations. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in a single file. For a skill of this size it's borderline acceptable, but the vault structure details and CLI reference could be split out, and there are no references to any supplementary files. | 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
- attilaczudor/Test
- Commit
b3cef5f
- 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.