obsidian
Composable Obsidian vault operations via CLI. Use when ANY task needs to read, write, search, tag, or query the Obsidian vault. This is the ONLY correct way to interact with the vault. Provides typed wrappers around the Obsidian CLI (v1.12+). Requires Obsidian to be running. Use when user says "save to vault", "obsidian", "research note", "daily note", "tag", "summarize and save", or any vault operation.
90
Quality
88%
Does it follow best practices?
Impact
93%
4.89xAverage score across 3 eval scenarios
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope (Obsidian vault operations), lists concrete actions, and provides excellent trigger term coverage. The explicit 'Use when...' clause with natural user phrases and the emphasis that this is 'the ONLY correct way to interact with the vault' helps Claude make confident selection decisions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, search, tag, or query the Obsidian vault' and 'typed wrappers around the Obsidian CLI'. Also mentions specific operations like 'save to vault', 'daily note', 'summarize and save'. | 3 / 3 |
Completeness | Clearly answers both what ('Composable Obsidian vault operations via CLI', 'typed wrappers around the Obsidian CLI') AND when ('Use when ANY task needs to read, write, search, tag, or query the Obsidian vault') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'save to vault', 'obsidian', 'research note', 'daily note', 'tag', 'summarize and save', 'vault operation'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Obsidian vault operations. The explicit mention of 'Obsidian CLI', 'vault', and Obsidian-specific terms like 'daily note' make it highly distinguishable from general note-taking or file management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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 skill with excellent actionability - the PowerShell heredoc examples and Python API reference are immediately usable. The workflow clarity is strong with explicit validation steps and self-healing patterns. However, the skill is lengthy and could benefit from splitting Agent Memory and Friction Self-Healing into separate referenced files to improve progressive disclosure and reduce token load.
Suggestions
Extract the 'Agent Memory (Composable)' section into a separate AGENT-MEMORY.md file and reference it from the main skill
Extract the 'Friction Self-Healing (Composable)' section into a separate SELF-HEALING.md file to reduce main skill length
Condense the heredoc escaping explanation - the warning about double-quoted heredocs could be a single line rather than a detailed explanation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes some verbose sections like the Agent Memory format explanation and the Friction Self-Healing workflow that could be condensed. The heredoc escaping explanation is necessary but lengthy. | 2 / 3 |
Actionability | Excellent executable examples throughout - PowerShell heredoc patterns, Python API calls, and CLI commands are all copy-paste ready. The Quick Reference section provides comprehensive, concrete method signatures with clear parameters. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation (verification notes section, deduplication before creating memories, upgrade workflow with numbered steps). The self-healing workflow includes explicit checkpoints and decision points for P0/P1/P2 priorities. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long and monolithic. The Agent Memory and Friction Self-Healing sections could potentially be separate files. References to external files (cli_sync.py, README.md) exist but the main content is dense. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.