Content
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 strong, well-structured testing skill that provides clear workflows, executable code examples, and concrete guidance across unit, integration, and E2E testing. The use of tables for dense information (anti-patterns, coverage requirements, context limits) is effective and token-efficient. The main weakness is that referenced external files (browser-testing skill, validation-gates, project.instructions.md) aren't available in the bundle, making it hard to fully assess progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured using tables for dense information delivery. It avoids explaining what testing is or how libraries work, and every section adds actionable value. No unnecessary padding or concept explanations. | 3 / 3 |
Actionability | Provides fully executable code examples for both unit tests (Vitest with mocking) and E2E tests (Playwright), concrete shell commands for running tests, and specific coverage targets. The anti-patterns table gives concrete correct approaches rather than vague advice. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with an explicit fix loop (step 5: 'If any step fails → fix → re-run from step 2'). The post-implementation checklist serves as a validation checkpoint, and E2E context limits provide guardrails for session management. | 3 / 3 |
Progressive Disclosure | References to external resources (browser-testing skill, validation-gates Gate 3, project.instructions.md) are present and clearly signaled in a references table. However, no bundle files are provided to support these references, and the E2E context limits section and coverage requirements could potentially be split out for a cleaner overview. The skill is reasonably well-organized but slightly heavy for a single file. | 2 / 3 |
Total | 11 / 12 Passed |