Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
75
62%
Does it follow best practices?
Impact
98%
2.57xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/verify/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description focuses almost entirely on when to use the skill but fails to explain what it actually does in concrete terms. It lacks specific actions, comprehensive trigger terms, and enough detail to clearly distinguish it from other validation or code-quality skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Runs linting, type checking, unit tests, and formatting checks for React contributions.'
Include more natural trigger terms users might say, such as 'lint', 'pre-commit', 'CI checks', 'code review', 'pull request', or 'test suite'.
Expand the 'what' portion to clearly describe the skill's capabilities so Claude can distinguish it from other validation or testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'validate changes' and 'check all React contribution requirements' but does not list any concrete actions (e.g., run linting, run tests, check formatting). The actions are vague and abstract. | 1 / 3 |
Completeness | The description provides a 'Use when' clause addressing when to use the skill, but the 'what does this do' part is essentially missing—it never explains what concrete actions the skill performs, only vaguely references validation and checking requirements. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'validate changes', 'committing', and 'React contribution requirements', but misses common variations users might say such as 'lint', 'pre-commit checks', 'CI checks', 'code quality', or 'pull request validation'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Validate changes before committing' is somewhat generic and could overlap with general linting, testing, or CI skills. The mention of 'React contribution requirements' adds some specificity but is still fairly broad. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured orchestration skill that clearly defines a verification workflow with sequential and parallel steps. Its main weakness is that the references to '/flow' and '/test' skills and the $ARGUMENTS parameter could be more explicit about how they're invoked and how arguments are passed through. Overall it's effective for its purpose.
Suggestions
Show how $ARGUMENTS is passed to the /test invocations (e.g., 'Use /test with pattern $ARGUMENTS')
Briefly clarify what /flow and /test refer to (e.g., 'Use /flow (type-check skill)') so the delegation is unambiguous
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations—every line serves a purpose. Assumes Claude knows what yarn, linting, type checking, and testing are. | 3 / 3 |
Actionability | Provides concrete commands (yarn prettier, yarn linc) but references '/flow' and '/test' without explaining what these are or how to invoke them. The $ARGUMENTS parameter usage is mentioned but not shown in the actual commands. Missing specifics on how subagents are launched. | 2 / 3 |
Workflow Clarity | Clear sequential-then-parallel workflow with explicit stop-on-failure checkpoints at each step. Includes error handling guidance (stop immediately, report with suggested fixes) and a success path. The sequence is unambiguous. | 3 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines with no need for external references, the content is well-organized with clear sections (Arguments, Instructions). References to /flow and /test appropriately delegate to other skills rather than inlining their content. | 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.
cafd63b
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.