jbvc/testing-patterns
Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.
82
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
92%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 a strong skill description that clearly communicates both capabilities and trigger conditions. It uses concrete terminology that users would naturally employ when seeking testing help. The only minor weakness is potential overlap with other testing-related skills, though the Jest and TDD specificity helps differentiate it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: Jest testing patterns, factory functions, mocking strategies, and TDD workflow. These are distinct, concrete capabilities rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what ('Jest testing patterns, factory functions, mocking strategies, and TDD workflow') and when ('Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'unit tests', 'test factories', 'TDD', 'red-green-refactor', 'Jest', 'mocking'. These cover common variations of how users would describe testing needs. | 3 / 3 |
Distinctiveness Conflict Risk | While Jest and TDD are fairly specific, 'unit tests' and 'mocking strategies' could overlap with other testing-related skills (e.g., a general testing skill, or framework-specific testing skills like Vitest or Mocha). The Jest specificity helps but doesn't fully eliminate conflict risk. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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, actionable testing patterns skill with excellent executable code examples covering factories, mocking, queries, and interactions. Its main weaknesses are verbosity in philosophical sections that Claude already understands, and a lack of demonstrated TDD workflow with explicit validation steps. The content would benefit from trimming known concepts and potentially splitting detailed patterns into separate referenced files.
Suggestions
Remove or drastically shorten the 'Testing Philosophy' section — Claude already knows TDD and BDD principles. Keep only project-specific conventions.
Add a concrete TDD walkthrough showing the red-green-refactor cycle with actual before/after code to improve workflow clarity.
Consider splitting detailed mocking patterns and anti-patterns into separate referenced files (e.g., MOCKING.md, ANTI_PATTERNS.md) to improve progressive disclosure.
Remove the 'Best Practices' bullet list at the end since each point is already demonstrated in the code examples above it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary philosophical preamble (TDD philosophy, behavior-driven testing principles) that Claude already knows. The 'Best Practices' summary at the end largely repeats what was already shown. However, the code examples themselves are reasonably tight. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code examples throughout — factory functions, custom render wrappers, mocking patterns, query patterns, and user interaction patterns are all copy-paste ready with concrete imports and assertions. | 3 / 3 |
Workflow Clarity | The TDD workflow is mentioned (red-green-refactor) but not demonstrated with a concrete step-by-step example showing the cycle in action. Test structure is shown but there are no validation checkpoints or feedback loops for when tests fail or need debugging. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a long monolithic file (~180 lines of content) where some sections (e.g., detailed mocking patterns, anti-patterns) could be split into referenced files. The 'Integration with Other Skills' section at the end hints at cross-references but doesn't provide navigable links. | 2 / 3 |
Total | 9 / 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.
Reviewed
Table of Contents