- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add testdouble/han --skill spike-consumer-baseline -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add testdouble/han --skill spike-consumer-baseline -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add testdouble/han --skill spike-consumer-baseline -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add testdouble/han --skill spike-consumer-baseline -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/testdouble/han/tree/HEAD/docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-baselineFrom the publisher
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.
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
---name: spike-consumer-baselinedescription: OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the…---# docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-baseline/SKILL.mdOverview
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.
FAQ
Download docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-baseline/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/testdouble/han.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.