testing-workflow
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, and flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
100
100%
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 (test plan generation, test file writing, coverage gap identification, anti-pattern detection) and provides explicit trigger guidance via a comprehensive 'Use when...' clause. The description uses proper third-person voice, includes natural user-facing keywords, and occupies a clear niche in the testing domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, and flags common testing anti-patterns. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates test plans, writes test files, identifies coverage gaps, flags anti-patterns) and 'when' with an explicit 'Use when...' clause listing six trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'tests', 'test suites', 'test strategies', 'mocking dependencies', 'code coverage', 'test planning', 'unit/integration/E2E'. These cover a wide range of natural user phrasings around testing. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to software testing with distinct triggers like 'test suites', 'mocking dependencies', 'code coverage', and 'test planning'. Unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers the full testing lifecycle—planning, implementation, E2E, and validation—with concrete examples and clear workflows. The use of tables for structured information (anti-patterns, coverage requirements, E2E limits) is excellent for token efficiency. The fix loop, mandatory browser testing gate, and post-implementation checklist provide strong validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured using tables for dense information delivery. No unnecessary explanations of what testing is or how libraries work—it assumes Claude knows Vitest, Playwright, and testing concepts. | 3 / 3 |
Actionability | Provides fully executable code examples for both unit tests (with mocking) and E2E tests (Playwright), concrete shell commands for running tests, and specific coverage targets. The examples are copy-paste ready and demonstrate real patterns. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with an explicit fix loop (step 5: fix → re-run from step 2). Includes a post-implementation checklist for validation, E2E context limits as guardrails, and the mandatory browser testing checkpoint before marking complete. | 3 / 3 |
Progressive Disclosure | SKILL.md serves as a comprehensive overview with clear one-level-deep references to browser-testing skill, validation-gates Gate 3, and project.instructions.md. Content is appropriately structured with tables and sections for easy scanning without being monolithic. | 3 / 3 |
Total | 12 / 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.
- Repository
- monkilabs/opencastle
- Commit
18c6f2c
- 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.