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.
npx skills add testdouble/han --skill spike-consumer-adversarial --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 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`. ## 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 these four facts: the incident ID, the primary error code, the peak latency figure, and the affected service name. ## Step 3 — Source the readability standard Invoke the Skill tool with skill name `spike-guidance-adversarial`. ## Step 4 — Draft the report Write the incident post-mortem with these five labeled sections, applying the readability standard: 1. **Summary** — names the incident ID and the affected service. 2. **Impact** — states the peak latency figure. 3. **Root cause** — names the primary error code. 4. **Resolution** — how it was mitigated. 5. **Follow-up actions** — at least two. ## Step 5 — Self-check Check the draft against the standard. ## Step 6 — Write the artifact and emit the completion token 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 | T
- 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-adversarial skill do?
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.
How do I install it?
Run `npx skills add testdouble/han --skill spike-consumer-adversarial --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.