Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/spike-consumer-forked
OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
1 of 23 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 1 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
When building an incident report for trial trial_612 in /var/trials from /data/inc_612.json, confirm the ordering requirement between Step 2 (extracting key facts) and Step 3/4 (sourcing standards and drafting text).
| Checked | Without skill | With skill |
|---|---|---|
| Records key facts in a working note before sourcing readability standards. | Missed | Passed |
| Incorporates all four extracted system facts into the completion token line. | 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.
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. Invoke the Skill tool with skill name spike-guidance-forked. Absorb the standard it surfaces.
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 with the skill
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.