Content
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 |