- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdouble/han --skill spike-consumer-inline -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdouble/han --skill spike-consumer-inline -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdouble/han --skill spike-consumer-inline -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add testdouble/han --skill spike-consumer-inline -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/testdouble/han/tree/HEAD/docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-inlineDe l'éditeur
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-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.
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, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explici
---name: spike-consumer-inlinedescription: OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the…---# docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-inline/SKILL.mdVue d'ensemble
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.
FAQ
Téléchargez docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-inline/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/testdouble/han.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.