testing-workflow

Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-structured, and highly actionable with concrete commands and thresholds. Its main weakness is workflow clarity: the testing workflow is expressed as rules and tables rather than a sequenced process with an explicit coverage-recovery feedback loop.

Suggestions

Add a short numbered testing workflow (e.g., 1. write unit/integration tests, 2. run 'npx vitest run --coverage', 3. if below minimums, add tests and re-run, 4. run E2E via 'npx playwright test', 5. log to .opencastle/logs/e2e-results.md) to give an explicit sequence with a coverage feedback loop.

Include a minimal copy-paste test-file template (e.g., a vitest unit test stub and a playwright E2E stub) to push actionability from mostly-executable to fully copy-paste ready.

Make the coverage-recovery loop explicit: state what to do when a layer falls below its minimum (write more tests for the gap, re-run, repeat) so the verification step has a clear feedback path.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven content with no over-explanation of basic testing concepts; every rule and threshold earns its place and assumes Claude's competence, matching the lean-and-efficient anchor.	5 / 5
Actionability	Provides concrete executable commands ('npx vitest run --coverage', 'npx playwright test', 'evaluate_script() over take_snapshot()') and specific paths/thresholds, but lacks a full copy-paste test-file template, keeping it just below the fully-executable anchor at 5.	4 / 5
Workflow Clarity	A mandatory browser-testing gate and verification commands provide checkpoints, but the overall test→measure→fix sequence is presented as rules rather than numbered steps and lacks an explicit feedback loop when coverage minimums are unmet — the batch-operation cap holds it at 3.	3 / 5
Progressive Disclosure	A short (~35 line) single-purpose skill with clear section headers and one well-signaled one-level-deep pointer (suite files in '.opencastle/project.instructions.md'), matching the well-organized simple-skill anchor.	5 / 5
	Total	17 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: concrete actions, explicit 'Use when' triggers, and a clear what/when structure. The only gaps are a few natural trigger synonyms and minor overlap risk with broader coding skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns' — matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both what (generates plans, writes files, identifies gaps, flags anti-patterns) and when ('Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural coverage ('writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage') but missing common standalone variations like 'unit tests' or 'integration tests' as triggers, so it sits just below the comprehensive-synonym anchor at 5.	4 / 5
Distinctiveness Conflict Risk	Testing is a mostly distinct niche, but trigger phrases like 'mocking dependencies' and 'test planning' overlap with general coding/implementation skills, keeping it just below the clear-niche anchor at 5.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/skills/testing-workflow/SKILL.md
Commit: fa0c341

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.