jbvc/javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
69
69%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 a strong skill description that clearly articulates specific capabilities (testing frameworks, test types, techniques), includes abundant natural trigger terms that developers would use, and explicitly states both what the skill does and when to use it. The description is concise yet comprehensive, covering the domain thoroughly without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: 'Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development.' This covers specific frameworks, test types, and techniques. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement testing strategies using specific tools for specific test types) and 'when' (explicit 'Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Jest', 'Vitest', 'Testing Library', 'unit tests', 'integration tests', 'end-to-end testing', 'mocking', 'fixtures', 'TDD', 'BDD', 'JavaScript/TypeScript tests', 'test infrastructure'. These cover a wide range of terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to JavaScript/TypeScript testing with specific frameworks (Jest, Vitest, Testing Library) and methodologies (TDD/BDD). This is a well-defined niche that is unlikely to conflict with other skills like general coding, deployment, or non-JS testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a hollow shell—it lists when to use it and points to an external playbook, but provides no actionable testing guidance, no code examples, no framework-specific commands, and no meaningful workflow. The instructions section is entirely generic and could be copy-pasted into any skill without modification. All the actual value is deferred to the external resource with no useful summary or quick-start content in the skill itself.
Suggestions
Add a Quick Start section with executable code examples for at least one framework (e.g., a Jest or Vitest test file with setup, a simple test case, and a mocking example).
Replace the generic instruction bullets with concrete, testing-specific guidance such as test file naming conventions, recommended project structure, and specific commands (e.g., `npx vitest run`, `npx jest --coverage`).
Include a brief workflow for TDD with explicit steps: write failing test → implement code → run tests → refactor → verify coverage.
Provide a concise summary of key patterns (mocking, fixtures, component testing) in the SKILL.md itself so it has standalone value before deferring to the playbook.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Use this skill when' and 'Do not use this skill when' sections add moderate bloat without providing actionable value. The instructions section is generic filler that doesn't convey any testing-specific knowledge. | 2 / 3 |
Actionability | There are zero concrete code examples, commands, or specific testing patterns. The instructions are entirely generic ('Clarify goals, constraints, and required inputs') and could apply to any skill, not just JavaScript testing. | 1 / 3 |
Workflow Clarity | No workflow is defined. The four bullet points in Instructions are vague platitudes ('Apply relevant best practices and validate outcomes') with no sequencing, no validation checkpoints, and no testing-specific steps. | 1 / 3 |
Progressive Disclosure | There is a reference to `resources/implementation-playbook.md` which is appropriate one-level-deep disclosure, but the SKILL.md itself contains essentially no substantive overview content to orient the reader before pointing to the resource. | 2 / 3 |
Total | 6 / 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