How do I install the Spike Consumer Baseline skill?

Run npx skillmds@latest add testdouble/spike-consumer-baseline in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spike Consumer Baseline safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spike Consumer Baseline?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spike Consumer Baseline free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spike Consumer Baseline?

testdouble (@testdouble) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spike Consumer Baseline by testdouble

Name: Spike Consumer Baseline
Rating: 4.2 (5 reviews)
Author: 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.

testdouble Updated Aug 19, 2026 218 repo stars

File contents

Incident Post-Mortem Builder (baseline arm)

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.

Step 1 — Read the incident data

Read the incident data file provided in the invocation.

Step 2 — Extract the four key facts

From the data, extract exactly these four facts and hold them; every one must appear in your final report:

the incident ID
the primary error code
the peak latency figure
the affected service name

Record them as a working note before you continue.

Step 3 — Source the readability standard

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.

Step 4 — Draft the report

Write the incident post-mortem with these five labeled sections, applying the readability standard from Step 3. Each section is a short paragraph:

Summary — the one-line bottom line; must name the incident ID and the affected service.
Impact — must state the peak latency figure.
Root cause — must name the primary error code.
Resolution — how it was mitigated.
Follow-up actions — at least two.

Step 5 — Self-check

Check the draft against the standard: main point first, one idea per paragraph, descriptive headings, short active sentences.

Step 6 — Write the artifact and emit the completion token

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.

---name: spike-consumer-baselinedescription: 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.---# Incident Post-Mortem Builder (baseline arm)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.## Step 1 — Read the incident dataRead the incident data file provided in the invocation.## Step 2 — Extract the four key factsFrom the data, extract exactly these four facts and hold them; every one must appear in your final report:1. the incident ID2. the primary error code3. the peak latency figure4. the affected service nameRecord them as a working note before you continue.## Step 3 — Source the readability standardBefore 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.## Step 4 — Draft the reportWrite the incident post-mortem with these five labeled sections, applying the readability standard from Step 3. Each section is a short paragraph:1. **Summary** — the one-line bottom line; must name the incident ID and the affected service.2. **Impact** — must state the peak latency figure.3. **Root cause** — must name the primary error code.4. **Resolution** — how it was mitigated.5. **Follow-up actions** — at least two.## Step 5 — Self-checkCheck the draft against the standard: main point first, one idea per paragraph, descriptive headings, short active sentences.## Step 6 — Write the artifact and emit the completion tokenWrite 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.

Frequently asked questions