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.
83
77%
Does it follow best practices?
Impact
93%
4.89xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/obsidian/SKILL.mdQuality
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 CLI operations), lists concrete actions (read, write, search, tag, query), and provides explicit trigger guidance with natural user phrases. It also includes useful technical context (CLI v1.12+, requires Obsidian running) and establishes itself as the exclusive skill for vault interactions, minimizing conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: read, write, search, tag, query the Obsidian vault. Also mentions typed wrappers around the Obsidian CLI with version specificity (v1.12+) and the requirement that Obsidian must be running. | 3 / 3 |
Completeness | Clearly answers both 'what' (composable Obsidian vault operations via CLI — read, write, search, tag, query) and 'when' (explicit 'Use when' clause with specific trigger phrases and a general rule about any vault operation). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'save to vault', 'obsidian', 'research note', 'daily note', 'tag', 'summarize and save', plus the general 'vault operation'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets Obsidian vault operations specifically, with clear niche triggers like 'obsidian', 'vault', 'daily note'. The emphatic statement that this is the 'ONLY correct way to interact with the vault' further reduces conflict risk by establishing exclusivity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable guidance with excellent code examples and clear workflows including validation steps. However, it is severely bloated — the Agent Memory, Friction Self-Healing, and composition sections should be separate files, and the main SKILL.md should be a concise overview with references. The content quality is high but the organization and token efficiency are poor.
Suggestions
Extract Agent Memory section into a separate AGENT-MEMORY.md and reference it with a one-line link from the main skill
Extract Friction Self-Healing section into a separate SELF-HEALING.md — this is a cross-cutting concern, not core to vault operations
Move the Quick Reference API listing to a REFERENCE.md file, keeping only the 3-4 most common operations inline
Move Composing with Other Skills examples to a COMPOSING.md file, since these are integration patterns not needed for basic usage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines. The Agent Memory section (~80 lines), Friction Self-Healing section (~60 lines), and Composing with Other Skills section are all substantial content that could be in separate files. The self-healing workflow example is repeated in detail, and the 'What NOT to do' section explains things Claude would understand from the positive examples alone. | 1 / 3 |
Actionability | Excellent executable examples throughout — PowerShell heredoc pipes, complete Python API reference with real method signatures, CLI commands for upgrading, and concrete memory note format. Every operation has copy-paste ready code. | 3 / 3 |
Workflow Clarity | The upgrade workflow has clear numbered steps with validation (diff → guide → update → save). The self-healing workflow has explicit sequencing with priority-based decision points. Verification notes explain how to confirm create operations succeeded via follow-up reads. Deduplication has a clear search-then-decide flow. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text. The Agent Memory section (~80 lines), Friction Self-Healing section (~60 lines with a full example), and Composing with Other Skills section should all be in separate referenced files. The Quick Reference API listing alone is ~60 lines that could be in a REFERENCE.md. Everything is inline with no external file references for detailed content. | 1 / 3 |
Total | 8 / 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 | |
- Repository
- 0xrabbidfly/eric-cartman
- Commit
1e34e1c
- 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.