Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/wjttc-tester
F1-inspired test EXECUTOR + reporter. Runs a test plan, finds and reproduces bugs, audits suite signal integrity, then files a WJTTC report (Brake/Engine/Aero/Tyre/Pit) with a tier verdict.
Passed 17 of 21 test cases with the skill, and 5 of 21 without it.
and 13 more in the full report
13 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our automated test suite achieved a 99% pass rate with zero Brake failures. What standard tier verdict and symbol apply to 99%?
| Checked | Without skill | With skill |
|---|---|---|
| Maps 99% pass rate to Gold ★ verdict | Missed | Passed |
The instructions your model reads when the skill loads.
"We break things so others never have to know they were broken."
Apply F1-inspired standards to software testing. When brakes must work flawlessly at race pace, so must the code in production. This skill executes test plans and files reports — it is the driver, not the engineer. To plan and generate the suite, use wjttc-builder.
Triage every test by blast radius. The first three set severity; Tyre and Pit cover durability and the release gate.
| Tier | Symbol | Meaning | Examples |
|---|---|---|---|
| Brake | 🚨 | Life-critical — failure is catastrophic | data loss, auth bypass, payment errors, destructive ops without confirm |
| Engine | ⚡ | Performance-critical — wrong results / poor UX | API accuracy, data transforms, calculations, format compliance, perf |
| Aero | 🏁 | Polish & edge cases — minor inconvenience | UI quirks, rare message formatting, optional-feature edges, docs |
| Tyre | 🛞 | Durability under load — degradation over time | stress/volume, concurrency, memory growth, large inputs |
| Pit | 🔧 | Release gate — the stop that lets you go | smoke/regression suite, CI green, the WJTTC report filed |
Test Brake first. If the brakes don't work, nothing else matters.
Red CI is a contract: it must always mean "stop, look, fix." A suite with high coverage but flaky reds is less trustworthy than a smaller suite with zero false alarms — because the team has stopped reading the reds. Fix the signal before you add more tests.
Method — classify the last 30 days of CI failures:
| Bucket | Definition | Verdict |
|---|---|---|
| Real bug | Red mapped to a real defect; fixed by a code change | ✓ Signal worked |
| Flake | Timing/network/concurrency noise; passed on rerun, no code change | ✗ Test design defect |
| Infra | Missing secret, runner image change, upstream dep — not the code | ✗ Workflow design defect |
test cases passed, vs 5 / 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.