- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill spike-consumer-inline -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill spike-consumer-inline -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill spike-consumer-inline -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill spike-consumer-inline -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/testdouble/han/tree/HEAD/docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-inlineDo 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-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.mdVisão geral
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.
Perguntas frequentes
Baixe docs/plans/han-communication-plugin/artifacts/oi-3-spike/harness-skills/spike-consumer-inline/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/testdouble/han.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.