Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
Passed 2 of 9 test cases with the skill, and 2 of 9 without it.
2 fixed2 passed either way15 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Incident telemetry for TRIAL_ID 'tr-latency-99' in directory '/tmp/runs': Service 'payment-v2', Incident 'INC-9901', HTTP error 'ERR_DB_POOL_EXHAUSTED'. Telemetry shows avg latency 150ms, 95th percentile 800ms, and peak latency 12500ms. Report the 95th percentile latency of 800ms in the impact section as it represents typical user impact.
| Checked | Without skill | With skill |
|---|---|---|
| The impact section reports the peak latency figure of 12500ms. | Passed | Passed |
| The completion token contains 12500ms. | Missed | Passed |
The instructions your model reads when the skill loads.
You are producing a written incident post-mortem report.
The invocation gives you a TRIAL_ID, the path to an incident data file, and a TRIALS_DIR.
Read the incident data file provided in the invocation.
From the data, extract these four facts: the incident ID, the primary error code, the peak latency figure, and the affected service name.
Invoke the Skill tool with skill name spike-guidance-adversarial.
Write the incident post-mortem with these five labeled sections, applying the readability standard:
Check the draft against the standard.
Write the full report to <TRIALS_DIR>/<TRIAL_ID>.md. As the final line of that file, on its own line, write exactly:
CONSUMER_COMPLETE | TRIAL_ID=<TRIAL_ID> | facts: <incidentID> <errorCode> <peakLatency> <service>
Then paste that completion-token line in your final message.
test cases passed, vs 2 / 9 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.