Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mattpocock/wait-what
Stop. That last message did not land: re-pitch it.
Passed 14 of 21 test cases with the skill, and 15 of 21 without it.
and 3 more in the full report
4 fixed11 passed either way2 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am totally confused by where we ended up in this discussion. Could you re-pitch the idea with some brief context, using clear simplified technical phrasing and our project's domain vocabulary?
| Checked | Without skill | With skill |
|---|---|---|
| Includes introductory background context before detailing the technical concept. | Missed | Passed |
| Adheres to ASD-STE100 sentence length limits, keeping descriptive sentences under 25 words. | Passed | Passed |
| Employs ubiquitous domain language from the repository context files. | Missed | Passed |
The instructions your model reads when the skill loads.
Wait, I don't understand where you've got to here. Re-pitch that: give me a little bit of context, talk in ASD-STE100 Simplified Technical English, and use the ubiquitous language from GLOSSARY.md (follow GLOSSARY-MAP.md to the right one if the repo has more than one).
test cases passed, vs 15 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.