obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
97
96%
Does it follow best practices?
Impact
100%
16.66xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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, well-crafted description that clearly identifies the tool (Obsidian CLI), lists specific capabilities across two domains (vault management and plugin/theme development), and includes an explicit 'Use when...' clause with natural trigger terms. It is distinctive, comprehensive, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read, create, search, manage notes/tasks/properties, reload plugins, run JavaScript, capture errors, take screenshots, inspect the DOM. Very comprehensive. | 3 / 3 |
Completeness | Clearly answers both 'what' (interact with Obsidian vaults via CLI for notes, tasks, properties, plugin/theme development) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Obsidian vault', 'notes', 'tasks', 'search', 'plugin', 'theme', 'command line', 'DOM', 'debug'. Good coverage of both note management and development use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets Obsidian specifically via CLI, combining vault management and plugin/theme development. The mention of 'Obsidian CLI', 'Obsidian vault', and 'Obsidian plugins and themes' creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that is concise, actionable, and well-structured. It efficiently teaches the Obsidian CLI syntax, file/vault targeting, common patterns, and plugin development workflow with concrete executable examples. The only minor weakness is the lack of supporting bundle files for progressive disclosure, though the content is organized well enough that this is a minor issue.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what Obsidian is, what CLIs are, and how bash works. Every section delivers new, non-obvious information (syntax quirks, file targeting behavior, vault targeting). No wasted tokens on explanations of basic concepts. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready bash commands throughout. The common patterns section gives a comprehensive set of executable examples covering reads, creates, searches, properties, tasks, and daily notes. Plugin development commands are equally specific and executable. | 3 / 3 |
Workflow Clarity | The plugin development cycle is a clear numbered sequence with explicit validation checkpoints: reload → check errors → verify visually → check console. It includes an explicit feedback loop ('if errors appear, fix and repeat from step 1'). The non-development commands are single-step operations that don't require multi-step workflows. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and references to `obsidian help` and external docs. However, with no bundle files, there's no actual progressive disclosure to separate files. The common patterns section is somewhat long and could potentially be split out, though it's not egregiously monolithic. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- kepano/obsidian-skills
- Commit
ac93987
- 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.