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.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/javascript-typescript/skills/javascript-testing-patterns/SKILL.mdQuality
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
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a comprehensive but excessively verbose testing reference that includes many trivial patterns Claude already knows (calculator tests, basic CRUD, simple hooks). While the code examples are high quality and fully executable, the content would be far more effective as a concise overview with references to separate pattern files. The lack of progressive disclosure and workflow guidance makes this more of a textbook chapter than an efficient skill document.
Suggestions
Reduce to a concise overview (~50-80 lines) covering framework setup and key decisions, then reference separate files like MOCKING_PATTERNS.md, INTEGRATION_TESTING.md, COMPONENT_TESTING.md for detailed examples.
Remove trivial examples (calculator add/divide, basic CRUD UserService, useCounter hook) that Claude already knows how to write—focus on non-obvious patterns like complex mocking, timer testing, and DI patterns.
Add a clear TDD workflow section with sequenced steps: 1. Write failing test → 2. Run and verify failure → 3. Implement minimal code → 4. Run and verify pass → 5. Refactor → 6. Run coverage check.
Trim the 15-item best practices list to 3-5 non-obvious items that Claude wouldn't already follow by default.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Includes many trivial patterns Claude already knows (testing pure functions like add/divide, basic class CRUD tests, simple hook tests). The calculator example, UserService CRUD, and useCounter hook are textbook examples that add no novel value. The 15-item best practices list restates common knowledge. | 1 / 3 |
Actionability | All code examples are fully executable TypeScript with complete implementations and corresponding test files. Config files, mock setups, and test patterns are copy-paste ready with proper imports and realistic scenarios. | 3 / 3 |
Workflow Clarity | The skill presents patterns but lacks a clear workflow for setting up testing from scratch or a TDD cycle. There's no sequenced process with validation checkpoints—it's a reference catalog of patterns rather than a guided workflow. The integration test section does show setup/teardown lifecycle but no explicit verification steps. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being far too long for a SKILL.md. The mocking patterns, integration testing, frontend testing, and fixtures sections should each be separate referenced files. The Resources section links to external URLs but doesn't organize internal content. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (1022 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.