post-incident-comms
Post an incident-comms update to the right Slack channel + thread; pairs with polymath-incident:comms-update for the body and respondToIncident for context.
- License 许可
- MIT
- 最近更新
- 2026-10-29
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- post-incident-comms
- description
- Post an incident-comms update to the right Slack channel + thread; pairs with polymath-incident:comms-update for the body and respondToIncident for context.
03 SKILL.md 正文
post-incident-comms
Take a comms-update draft (or write one) and post it to the right Slack channel + thread. Output is the posted ts so the next update can thread under it.
Mode: deterministic — same inputs, same output. Follow the steps and the output shape exactly; compute with the named script or tool, never by estimate; add nothing the shape does not ask for.
MCP binding (read before any tool call): if your host has a
slackMCP server, use its tools for this skill's data access. Check your own tool list — it may be registered under another name (a Claude Code connector appears asmcp__claude_ai_<Name>__*). Tool names differ between servers: use the closest match, and say so when the server is read-only. Never install or start a second copy. If there is none, work without MCP tool calls (give the user the queries or steps to run) and ask before suggesting an install.
When to use
- An incident comms update was drafted by
polymath-incident:comms-updateand needs to go out. - A
respondToIncidentworkflow step needs to broadcast progress. - A status-page-style update is going to the internal channel.
Inputs
- Update body (required) — or invoke
polymath-incident:comms-updatefirst to draft one. - Incident ID (required) — used to derive the channel name + locate the thread.
- Channel — explicit (
#inc-2026-09) or computed from the incident ID. Fall back touserConfig.defaultIncidentChannelwhen neither is supplied. - Parent thread
ts(optional) — when set, the post threads under it. When absent, this update opens a new thread and the returnedtsbecomes the thread root for follow-ups.
Procedure
- Resolve the channel. Prefer explicit channel input; fall back to
inc-<incident-id-slug>; fall back touserConfig.defaultIncidentChannel. If none resolves, surface and stop. - Look up the channel ID via the slack MCP's
conversations_list(orchannels.list). Slack APIs take channel IDs, not names. - Format the body —
polymath-incident:comms-updatealready produces a status / impact / next-update structure. Don't re-wrap; convert it to Slack mrkdwn (not a code block — code blocks don't wrap on mobile and aren't read well by screen readers). - Confirm with the comms lead / user. Show the channel, thread, and exact text and wait for approval — unless the user already approved this exact update (e.g. a workflow step that presented it).
- Post via the slack MCP's
chat_postMessagewith:channel: resolved ID.thread_ts: if a parent was supplied.text: a short fallback summary (Slack uses it for push notifications and screen-readers).blocks: rich layout with the structured fields. If the call errors or times out, read the channel/thread history for the message before retrying — a duplicate incident update is worse than a slow one.
- Return the posted message's
tsso the next update can thread under it. Save it as a step artifact (e.g.docs/incidents/<id>-slack-thread.ts). - Status-page channel mirror — for sev1/sev2, also post a one-line summary to the status-page channel (separate channel from the incident channel). The summary points back to the incident channel for thread continuation.
Output
post-incident-comms
Resolved channel: #inc-2026-09 (id C0XXXXXX)
Parent thread ts: 1716572400.000200
Posted ts: 1716572734.000300
Mirrored to: #status-page (one-line summary)
Saved thread root: docs/incidents/2026-09/slack-thread.ts
Quality bar
- Channel ID resolved before posting (not the name).
- Thread root saved as a step artifact so subsequent updates thread correctly.
- Status-page channel mirror for sev1/sev2 (one line, no body duplication).
- No PII in the fallback
textfield — it appears in push notifications.
Anti-patterns to avoid
- Calling
chat_postMessagewith the channel name. Some Slack APIs accept it; some don't. Resolve to ID. - Re-posting the full update to two channels — duplicate noise. Mirror is one line + a back-pointer.
- Posting without a thread when one exists. Splits the conversation.
- Logging the body to plain logs (PII risk). The slack MCP holds it; we don't.
04 同仓库更多 Skills
runbook
Write or refresh an operational runbook for an alert/symptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.
rfc
Draft a lightweight design RFC to docs/rfcs/<slug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).
editorial-pass
Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.
architecture-review-facilitation
Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.
architecture-doc
Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).
adr
Write an Architecture Decision Record (Michael Nygard format) to docs/adrs/NNNN-<slug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).