verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
97
Does it follow best practices?
Validation for skill structure
Discovery
89%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 well-structured description with clear 'Use when' triggers and good coverage of natural terms that would appear when completing work. The main weakness is that the specific verification actions could be more concrete (e.g., 'run tests', 'check build status') rather than the generic 'verification commands'. The philosophical tagline 'evidence before assertions always' adds clarity to the intent.
Suggestions
Replace 'running verification commands' with specific examples like 'run tests, check linter output, verify build passes' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (verification before claims) and some actions ('running verification commands', 'confirming output'), but doesn't list specific concrete actions like 'run tests', 'check linter', 'verify build passes'. | 2 / 3 |
Completeness | Clearly answers both what ('running verification commands and confirming output before making success claims') and when ('about to claim work is complete, fixed, or passing, before committing or creating PRs'). Has explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users/Claude would encounter: 'complete', 'fixed', 'passing', 'committing', 'creating PRs', 'success claims'. These are terms that naturally appear when finishing work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on verification before completion claims - distinct from general testing skills or commit message skills. The trigger context ('about to claim work is complete') is unique and unlikely to conflict. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill document that efficiently communicates a critical verification discipline. It uses tables, code blocks, and clear patterns to maximize information density while remaining highly actionable. The gate function provides an unambiguous workflow, and the rationalization prevention table anticipates common failure modes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and code blocks to convey information densely. No unnecessary explanations of concepts Claude already knows; every section earns its place with actionable guidance. | 3 / 3 |
Actionability | Provides concrete, executable patterns with clear examples of correct vs incorrect behavior. The gate function is a specific 5-step process, and the tables give precise mappings between claims and required evidence. | 3 / 3 |
Workflow Clarity | The gate function provides an explicit 5-step sequence with clear validation checkpoints. The regression test pattern explicitly shows the red-green verification cycle. Feedback loops are built into the core workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Overview, Gate Function, Common Failures, Red Flags, etc.). For a behavioral skill of this scope, the single-file format is appropriate and sections are logically ordered from principle to application. | 3 / 3 |
Total | 12 / 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.
- 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.