senior-qa
This skill should be used 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". Use for React/Next.js testing with Jest, React Testing Library, and Playwright.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill senior-qa85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 description has strong trigger term coverage and completeness with explicit 'when to use' guidance. However, it lacks specific concrete actions (what the skill actually does beyond generic test-related tasks) and could potentially conflict with other testing-related skills due to generic trigger terms. The description is structured backwards - leading with triggers rather than capabilities.
Suggestions
Add specific concrete actions like 'mock API responses', 'test component rendering', 'validate user interactions', 'generate snapshot tests' to improve specificity
Restructure to lead with capabilities first, then triggers: 'Tests React/Next.js components using Jest and React Testing Library, scaffolds E2E tests with Playwright, analyzes coverage. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React/Next.js testing) and mentions specific tools (Jest, React Testing Library, Playwright), but doesn't list concrete actions beyond generic terms like 'generate tests', 'write unit tests'. Lacks specific capabilities like 'mock API calls', 'test component rendering', or 'validate user interactions'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (React/Next.js testing with Jest, React Testing Library, and Playwright) and 'when' (lists specific trigger phrases at the start). The 'Use when...' equivalent is present via 'This skill should be used when...' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger 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'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies React/Next.js and particular testing frameworks, terms like 'generate tests' and 'write unit tests' could overlap with testing skills for other frameworks (Python, backend, etc.). The React/Next.js qualifier helps but isn't prominently positioned. | 2 / 3 |
Total | 10 / 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 well-structured, highly actionable skill with clear workflows and good progressive disclosure. The main weakness is moderate verbosity - the detailed output examples for each tool and some common patterns (MSW, RTL queries) that Claude already knows could be trimmed to improve token efficiency.
Suggestions
Remove or significantly condense the 'Output:' blocks showing example tool output - Claude can infer what these tools produce
Move the 'Common Patterns Quick Reference' section to a separate reference file since these are standard patterns Claude already knows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as detailed output examples for every tool and explanations of patterns Claude already knows (like basic RTL queries and MSW setup). The Table of Contents adds overhead for a skill of this size. | 2 / 3 |
Actionability | Provides fully executable code examples throughout - bash commands, TypeScript test code, Jest config, Playwright locators, and CI/CD YAML. All examples are copy-paste ready with realistic patterns. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps (Unit Test Generation, Coverage Analysis, E2E Setup). Each workflow includes validation checkpoints like 'Run tests and check coverage' and 'Verify improvement' steps. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, a reference table pointing to external docs (testing_strategies.md, test_automation_patterns.md, qa_best_practices.md), and appropriate separation between quick start, detailed tool docs, workflows, and quick reference patterns. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- 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.