Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
95
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 concisely covers specific capabilities, includes natural trigger terms, explicitly states when to use the skill, and is clearly distinguishable from other skills through Obsidian-specific terminology. It follows the recommended pattern of listing actions followed by a 'Use when' clause, and uses third person voice correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Search, create, and manage notes' along with specific features like 'wikilinks and index notes'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (search, create, manage notes with wikilinks and index notes) and 'when' (explicit 'Use when user wants to find, create, or organize notes in Obsidian'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'notes', 'Obsidian', 'vault', 'wikilinks', 'find', 'create', 'organize'. These cover common variations of how users would describe note-taking tasks in Obsidian. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'Obsidian vault', 'wikilinks', and 'index notes' creates a very clear niche. This is unlikely to conflict with generic note-taking or document management skills due to the Obsidian-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A clean, efficient skill that provides actionable commands and clear conventions for managing an Obsidian vault. Its main weakness is the lack of validation steps in the create workflow—there's no guidance on verifying that wikilinks resolve correctly or that new notes are linked from relevant index notes. Overall it's well-structured and respects Claude's intelligence.
Suggestions
Add a validation step to the 'Create a new note' workflow: after creating a note, verify that referenced wikilinks resolve to existing notes (e.g., grep for the target filenames) and update relevant index notes.
Consider adding a brief step to the create workflow for checking if a similar note already exists before creating a new one, to prevent duplicates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what Obsidian is, what wikilinks are conceptually, or how bash commands work. The vault path, conventions, and commands are stated directly without padding. | 3 / 3 |
Actionability | Provides fully executable bash commands for searching by filename, content, and backlinks. The create workflow gives concrete steps with specific conventions. Commands are copy-paste ready with the actual vault path. | 3 / 3 |
Workflow Clarity | Workflows are clearly listed and sequenced, but the 'Create a new note' workflow lacks a validation step—there's no check that wikilinks resolve to existing notes or that the note was properly added to a relevant index. For a vault management skill, verifying link integrity would be important. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with a flat, well-organized structure using clear section headers. No external references are needed, and the content is appropriately scoped for its purpose. | 3 / 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.
b843cb5
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.