- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add testdouble/han --skill spike-consumer-forked -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add testdouble/han --skill spike-consumer-forked -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add testdouble/han --skill spike-consumer-forked -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add testdouble/han --skill spike-consumer-forked -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/testdouble/han/tree/HEAD/docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-forkedDel publicador
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.
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 explic
---name: spike-consumer-forkeddescription: OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the…---# docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-forked/SKILL.mdResumen general
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.
Preguntas frecuentes
Descarga docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-forked/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/testdouble/han.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.