senior-qa
Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and configures test runners. Use when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality".
90
86%
Does it follow best practices?
Impact
92%
1.26xAverage score across 6 eval scenarios
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 an excellent skill description that clearly defines its scope (React/Next.js testing), lists multiple concrete actions with specific tooling references, and provides comprehensive trigger terms in an explicit 'Use when...' clause. It uses proper third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: scans components to create Jest + RTL test stubs, analyzes Istanbul/LCOV coverage reports, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and configures test runners. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates unit/integration/E2E tests, scans components, analyzes coverage, scaffolds Playwright files, mocks APIs, creates fixtures, configures runners) and 'when' with an explicit 'Use when...' clause listing eight specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'generate tests', 'write unit tests', 'analyze test coverage', 'scaffold E2E tests', 'set up Playwright', 'configure Jest', 'implement testing patterns', 'improve test quality'. Also includes technology-specific terms like Jest, Playwright, MSW, React Testing Library, Istanbul/LCOV. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: React/Next.js testing specifically, with named tools (Jest, RTL, Playwright, MSW, Istanbul/LCOV). Unlikely to conflict with general coding skills or non-testing skills due to the specificity of the technology stack and task domain. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-organized skill with strong actionability and good progressive disclosure. Its main weaknesses are some redundancy in the common patterns/commands sections (which largely cover knowledge Claude already has) and the lack of explicit validation checkpoints and error recovery steps in the multi-step workflows. The broken string literals in the generated test code examples (e.g., malformed expect statements) also slightly undermine quality.
Suggestions
Add explicit validation checkpoints and error recovery loops to workflows (e.g., 'If tests fail after generation, review errors, fix, and re-run before proceeding')
Remove or significantly trim the Common Patterns Quick Reference section—RTL queries, MSW setup, and Playwright locators are well-known to Claude and waste token budget
Fix the broken code examples (e.g., the Button.test.tsx has malformed string literals in expect/getByRole calls)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary verbosity. The 'Common Commands' section at the end repeats commands already shown in workflows. The Common Patterns Quick Reference section covers things Claude already knows well (RTL queries, MSW setup, Playwright locators). Some tightening is possible. | 2 / 3 |
Actionability | The skill provides fully executable commands, concrete TypeScript/JavaScript code examples, specific CLI invocations with flags, and copy-paste ready configurations for Jest, Playwright, MSW, and CI pipelines. The code examples are complete and specific. | 3 / 3 |
Workflow Clarity | The three workflows (Unit Test Generation, Coverage Analysis, E2E Setup) are clearly sequenced with numbered steps. However, there are no explicit validation checkpoints or error recovery feedback loops. For example, the unit test generation workflow doesn't include a 'if tests fail, fix and re-run' step, and the E2E setup has no validation that scaffolded tests actually pass before adding to CI. | 2 / 3 |
Progressive Disclosure | The skill has a clear Quick Start section, organized tool descriptions, detailed workflows, and a well-structured reference table pointing to one-level-deep external files (references/testing_strategies.md, etc.). Content is appropriately split between overview and detail. | 3 / 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
- alirezarezvani/claude-skills
- Commit
967fe01
- 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.