test
Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.
85
77%
Does it follow best practices?
Impact
100%
2.85xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/test/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.
The description is functional with a clear 'Use when' clause and a distinct niche (React core testing with specific channels). However, it lacks specificity in describing concrete actions beyond 'run tests' and could benefit from more natural trigger terms that users might use when seeking help with React testing.
Suggestions
Add more specific actions such as 'Run unit tests, integration tests, and build verification for React core packages'.
Include additional natural trigger terms users might say, such as 'jest', 'test suite', 'react test', 'CI checks', or 'test failures'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React core testing) and mentions specific channels (source, www, stable, experimental), but doesn't describe concrete actions beyond 'run tests'. Missing details like what kinds of tests, how they're run, or what outputs are produced. | 2 / 3 |
Completeness | Explicitly answers both 'what' (run tests for React core across multiple channels) and 'when' ('Use when you need to run tests for React core'). The 'Use when' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'tests', 'React core', and channel names (source, www, stable, experimental), but misses common variations users might say such as 'unit tests', 'jest', 'test suite', 'CI', or 'react testing'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to React core testing with named channels (source, www, stable, experimental), making it clearly distinguishable from general testing skills or other framework-specific testing skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
79%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-crafted, concise skill that provides highly actionable, project-specific guidance for running React tests across different release channels. Its main strengths are the precise command mappings and practical usage examples. Minor weaknesses include the lack of explicit error recovery steps in the workflow and the absence of bundle files to support the cross-reference to the feature-flags skill.
Suggestions
Add a brief feedback loop for test failures, e.g., 'If tests fail, check @gate pragmas and re-run with the correct channel; see feature-flags skill for flag details.'
Consider adding a brief example of actual test output (success vs failure) so Claude knows what to look for when reporting results.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place: usage examples, channel mappings, command mappings, and hard rules are all non-obvious, project-specific knowledge. No unnecessary explanations of what React or testing is. | 3 / 3 |
Actionability | Provides exact yarn commands for each channel, concrete usage examples with specific patterns, and clear flag mappings. Commands are copy-paste ready and the channel-to-command mapping table is fully specified. | 3 / 3 |
Workflow Clarity | The 3-step workflow (parse channel → map to command → report results) is clear and sequential. However, there's no validation/feedback loop for handling test failures beyond 'report results,' and the 'Common Mistakes' section hints at error scenarios without providing explicit recovery steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Usage Examples, Release Channels, Instructions, Hard Rules, Common Mistakes). References the 'feature-flags' skill appropriately. However, with no bundle files, the reference to the feature-flags skill cannot be verified, and the content is moderately long without any split into supporting files. | 2 / 3 |
Total | 10 / 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.
- Repository
- facebook/react
- Commit
cafd63b
- 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.