spike-consumer-inline
OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
Profile →npx skills add testdouble/han --skill spike-consumer-inline --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Incident Post-Mortem Builder (inline 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. ## 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: 1. the incident ID 2. the primary error code 3. the peak latency figure 4. 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. Invoke the Skill tool with skill name `spike-guidance-inline`. Absorb the standard it surfaces into your context. 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 1 — Read the incident data
- Step 2 — Extract the four key facts
- Step 3 — Source the readability standard
- Step 4 — Draft the report
- Step 5 — Self-check
- Step 6 — Write the artifact and emit the completion token
What does the spike-consumer-inline skill do?
OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.
How do I install it?
Run `npx skills add testdouble/han --skill spike-consumer-inline --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From testdouble/han, a repository with 154 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.