Install any skill in seconds. Free to start, no credit card required.
Get Started Free →elie222/qa-label
Label a PR as ready for QA so the QA server picks it up automatically
Passed 20 of 22 test cases with the skill, and 7 of 22 without it.
and 12 more in the full report
14 fixed6 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
What test suite is executed by the QA server once a pull request is labeled for QA?
| Checked | Without skill | With skill |
|---|---|---|
| States that browser tests are executed | Missed | Passed |
The instructions your model reads when the skill loads.
To mark a PR ready for QA, run: gh pr edit <PR_NUMBER> --add-label "ready-for-qa"
An automated QA process on the QA server will pick it up within ~60s and run browser tests against the PR branch. New pushes retrigger automatically while the label is present.
test cases passed, vs 7 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.