test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.
96
Does it follow best practices?
Validation for skill structure
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 hits all the marks. It provides specific, named testing patterns and techniques, includes comprehensive natural trigger terms users would actually say, has an explicit 'Use when...' clause with multiple scenarios, and carves out a distinct niche in testing practices that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete patterns and actions: 'Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles' - these are all concrete, named techniques. | 3 / 3 |
Completeness | Clearly answers both what (applies testing patterns to write maintainable test suites) AND when with explicit 'Use when...' clause covering six distinct trigger scenarios including test types, practices, and frameworks. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'integration tests', 'end-to-end tests', 'TDD', 'BDD', 'mocks, stubs, spies, or fakes', 'test coverage', 'flakiness', and specific frameworks like 'Jest, Vitest, pytest'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on testing patterns and practices with distinct triggers like 'TDD', 'BDD', 'mocks', 'test coverage', 'flakiness' - unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. The pattern selection guide and combination workflows provide clear navigation, and all code examples are executable. The main weakness is that the content is somewhat monolithic for its length—splitting detailed patterns into separate files would improve progressive disclosure.
Suggestions
Consider splitting individual pattern details into a separate PATTERNS_REFERENCE.md file, keeping only the selection guide, combination workflows, and brief pattern summaries in the main SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting patterns with minimal explanation and letting code examples speak for themselves. No unnecessary explanations of concepts Claude already knows. | 3 / 3 |
Actionability | Every pattern includes fully executable code examples that are copy-paste ready. The examples use real-world scenarios (UserService, Cart, OrderService) with concrete implementations. | 3 / 3 |
Workflow Clarity | The 'Pattern Combination Workflows' section explicitly shows how to sequence patterns for different test types. The verification checklist provides clear validation steps. The pattern selection guide helps users navigate to the right approach. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a helpful selection guide at the top, but this is a longer skill (~200 lines) that could benefit from splitting detailed pattern implementations into separate reference files while keeping the overview concise. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.