Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wordpress/testing
Use when writing, running, or debugging tests in the Gutenberg repository — JavaScript unit tests (Jest), PHP tests (PHPUnit), or end-to-end tests (Playwright).
Passed 20 of 22 test cases with the skill, and 10 of 22 without it.
and 8 more in the full report
10 fixed10 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which project reference file covers automated browser testing, page object patterns, and end-to-end test runner configuration?
| Checked | Without skill | With skill |
|---|---|---|
| Directs to references/e2e.md for end-to-end browser testing. | Missed | Passed |
The instructions your model reads when the skill loads.
Before writing any test bodies, draft the test names — behavior from the user's perspective, one behavior per case (see Describing tests) — and confirm the list with the author. Every proposed case must trace to the behavior being added or changed; do not pad the list with adjacent or unrelated coverage. If working unattended, put the proposed list in your summary for review instead.
No loosened assertions, no added waits or timeouts, no skipped cases without saying so. Diagnose the root cause, or report the failure honestly.
The e2e test passing is not the final task success criteria. The core goal is to verify that the production code works as expected.
test cases passed, vs 10 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.