vault-status
Show vault statistics, queue count, and reading suggestions. Use when the user wants an overview of their knowledge base.
80
Quality
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/vault-status/SKILL.mdQuality
Discovery
75%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 reasonably well-constructed description that successfully includes both 'what' and 'when' components with an explicit trigger clause. The main weaknesses are moderate specificity in describing the actual capabilities and limited trigger term coverage that could miss natural user phrasings like 'show me my dashboard' or 'what's in my reading queue'.
Suggestions
Add more specific details about what statistics are shown (e.g., 'total notes, tags, connections, unread items')
Expand trigger terms to include natural variations like 'dashboard', 'summary', 'reading list', 'backlog', or 'what do I have saved'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (vault/knowledge base) and lists some actions (show statistics, queue count, reading suggestions), but the actions are somewhat general and could be more concrete about what specific statistics or suggestions are provided. | 2 / 3 |
Completeness | Clearly answers both what (show vault statistics, queue count, reading suggestions) and when (when user wants an overview of their knowledge base) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes 'vault statistics', 'queue count', 'reading suggestions', and 'knowledge base' which are relevant, but misses common variations users might say like 'dashboard', 'summary', 'what's in my vault', 'reading list', or 'backlog'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'vault', 'queue count', and 'reading suggestions' creates a distinct niche that is unlikely to conflict with other skills. The knowledge base/vault terminology is specific enough to avoid overlap. | 3 / 3 |
Total | 10 / 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-structured, actionable skill with clear workflows and concrete examples. The main weakness is verbosity in the output format examples and some inline content that could be referenced externally. The skill effectively guides Claude through reading vault status and providing user-relevant suggestions.
Suggestions
Condense the output format examples - show one complete example rather than separate basic and detailed versions with overlapping content
Consider extracting the Quick Actions section to a separate reference file since it's supplementary to the core vault-status functionality
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the output format examples are verbose and the step-by-step breakdown could be tighter. The detailed output section repeats structural patterns unnecessarily. | 2 / 3 |
Actionability | Provides fully concrete, executable guidance with specific file paths, JSON structures, CLI commands, and exact output formats. The bash commands are copy-paste ready and the expected outputs are clearly specified. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with explicit instructions at each stage. Includes conditional logic (--detailed flag), action suggestions based on state, and specific commands for quick actions. The workflow is well-structured for a read-heavy operation. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The detailed output section and quick actions could potentially be split out, and there are no references to external documentation for the obsidian-cli tool. | 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.