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
Vault discovery and config reading
Reads obsidian.json
100%
100%
No hardcoded vault paths
100%
100%
Uses print-default for default vault
0%
100%
Falls back to open:true
100%
100%
Handles multiple vaults
100%
100%
Outputs vault paths
100%
100%
Marks active vault
100%
100%
README explains discovery
100%
100%
Uses obsidian-cli
100%
100%
Without context: $0.1951 · 53s · 11 turns · 15 in / 3,341 out tokens
With context: $0.2388 · 50s · 15 turns · 177 in / 2,997 out tokens
Safe note move and wikilink preservation
Uses obsidian-cli move
0%
100%
No mv/cp usage
0%
100%
Sets default vault
0%
100%
All 4 moves present
100%
100%
Correct destination paths
100%
100%
NOTES explains wikilinks
100%
100%
NOTES mentions obsidian-cli move advantage
30%
100%
Correct move syntax
0%
100%
Without context: $1.2231 · 3m 45s · 47 turns · 161 in / 11,874 out tokens
With context: $0.1900 · 39s · 14 turns · 16 in / 2,086 out tokens
Note search by name vs content
Uses search for titles
0%
100%
Uses search-content for body
0%
100%
Both commands present
0%
100%
Sets default vault
0%
100%
Report has two sections
100%
100%
Snippets in content section
46%
100%
Correct search query used
20%
100%
Without context: $0.2712 · 1m · 15 turns · 19 in / 3,631 out tokens
With context: $0.2108 · 43s · 15 turns · 19 in / 2,357 out tokens
Table of Contents
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.