obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 2.12xAgent success when using this skill
Validation for skill structure
Discovery
32%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 tool ecosystem (Obsidian, obsidian-cli) but is too vague about specific capabilities and completely lacks trigger guidance. It would benefit from listing concrete actions and adding explicit 'Use when...' conditions to help Claude distinguish this from general markdown or note-taking skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Obsidian', 'vault', 'knowledge base', 'PKM', 'backlinks', or 'note-taking'.
List specific concrete actions such as 'create notes', 'manage links', 'search vault contents', 'organize with tags', or 'sync vault structure'.
Include common file extensions and user phrases like '.md files', 'personal wiki', or 'second brain' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Obsidian vaults, Markdown notes) and mentions automation via obsidian-cli, but lacks specific concrete actions like 'create notes', 'link notes', 'search vault', or 'manage tags'. | 2 / 3 |
Completeness | Describes what at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Obsidian vaults', 'Markdown notes', and 'obsidian-cli' which are relevant, but misses common user terms like 'notes', 'knowledge base', 'PKM', 'backlinks', or '.md files'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Obsidian' and 'obsidian-cli' provide some distinctiveness, but 'plain Markdown notes' could overlap with general markdown editing skills; needs clearer Obsidian-specific triggers. | 2 / 3 |
Total | 7 / 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 strong, concise skill that efficiently teaches Obsidian vault interaction and CLI usage. It excels at actionability with concrete commands and paths, and respects token budget by assuming Claude's competence. The main gap is missing validation/verification guidance for potentially destructive operations like move and delete.
Suggestions
Add a brief validation step after move/delete operations (e.g., 'Verify with `obsidian-cli search` or check file exists')
Consider adding error handling guidance for common failures (e.g., vault not found, URI handler not working)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Obsidian or Markdown is. Every line provides actionable information Claude wouldn't inherently know (file paths, CLI commands, vault resolution logic). | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout (obsidian-cli set-default, search, create, move, delete). Includes specific file paths and flags. The guidance is immediately executable. | 3 / 3 |
Workflow Clarity | Commands are listed but lack explicit validation steps. For operations like move/delete, there's no verification workflow (check result, handle errors). The 'pick a default vault (once)' is a simple sequence but more complex workflows lack checkpoints. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, this is well-organized with clear sections (vault structure, finding vaults, CLI quick start). Content is appropriately scoped 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 | |
- 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.