Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/spike-consumer-baseline
OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
Passed 7 of 19 test cases with the skill, and 2 of 19 without it.
and 5 more in the full report
5 fixed3 passed either way15 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
When preparing to build a report for TRIAL_ID `trial-909` with data `/logs/909.json` into `/out/trials`, which four specific key facts must be extracted during Step 2 before drafting?
| Checked | Without skill | With skill |
|---|---|---|
| The extracted facts include incident ID, primary error code, peak latency, and affected service name. | Missed | Passed |
| The completion token includes all four extracted facts. | Missed | Passed |
The instructions your model reads when the skill loads.
You are producing a written incident post-mortem report. This skill has SIX steps. The steps below are the whole skill. Complete all six in order. Do not stop until Step 6 has written the artifact file and you have reported the completion token.
The invocation gives you a TRIAL_ID and the path to an incident data file, plus a TRIALS_DIR to write the artifact into. It also gives you a STANDARD_PATH to the readability standard file.
Read the incident data file provided in the invocation.
From the data, extract exactly these four facts and hold them; every one must appear in your final report:
Record them as a working note before you continue.
Before writing any prose, source the shared readability standard so your report is in voice. Read the file at STANDARD_PATH directly and absorb the standard.
Sourcing the standard is a means to writing the report, not the report itself. You are NOT done after this step. Continue immediately to Step 4.
Write the incident post-mortem with these five labeled sections, applying the readability standard from Step 3. Each section is a short paragraph:
Check the draft against the standard: main point first, one idea per paragraph, descriptive headings, short active sentences.
Write the full report to a file at <TRIALS_DIR>/<TRIAL_ID>.md. As the final line of that file, on its own line, write the completion token exactly in this form (substitute the real values):
CONSUMER_COMPLETE | TRIAL_ID=<TRIAL_ID> | facts: <incidentID> <errorCode> <peakLatency> <service>
Then, in your final message, state that all six steps are complete and paste that completion-token line verbatim.
test cases passed, vs 2 / 19 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.