[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74G7BFMBYSXBPRD53MC02XP":3,"skill-same:01M74G7BFMBYSXBPRD53MC02XP":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74G7BFMBYSXBPRD53MC02XP","post-incident-comms",null,"Post an incident-comms update to the right Slack channel + thread; pairs with polymath-incident:comms-update for the body and respondToIncident for context.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-chat\u002Fskills\u002Fpost-incident-comms\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: post-incident-comms\ndescription: Post an incident-comms update to the right Slack channel + thread; pairs with polymath-incident:comms-update for the body and respondToIncident for context.\n---\n\n# post-incident-comms\n\n> 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.\n\n**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.\n\n> **MCP binding (read before any tool call):** if your host has a `slack` MCP 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 as `mcp__claude_ai_\u003CName>__*`). 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.\n\n## When to use\n\n- An incident comms update was drafted by `polymath-incident:comms-update` and needs to go out.\n- A `respondToIncident` workflow step needs to broadcast progress.\n- A status-page-style update is going to the internal channel.\n\n## Inputs\n\n- Update body (required) — or invoke `polymath-incident:comms-update` first to draft one.\n- Incident ID (required) — used to derive the channel name + locate the thread.\n- Channel — explicit (`#inc-2026-09`) or computed from the incident ID. Fall back to `userConfig.defaultIncidentChannel` when neither is supplied.\n- Parent thread `ts` (optional) — when set, the post threads under it. When absent, this update opens a new thread and the returned `ts` becomes the thread root for follow-ups.\n\n## Procedure\n\n1. **Resolve the channel.** Prefer explicit channel input; fall back to `inc-\u003Cincident-id-slug>`; fall back to `userConfig.defaultIncidentChannel`. If none resolves, surface and stop.\n2. **Look up the channel ID** via the slack MCP's `conversations_list` (or `channels.list`). Slack APIs take channel IDs, not names.\n3. **Format the body** — `polymath-incident:comms-update` already produces a status \u002F impact \u002F 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).\n4. **Confirm with the comms lead \u002F 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).\n5. **Post** via the slack MCP's `chat_postMessage` with:\n   - `channel`: resolved ID.\n   - `thread_ts`: if a parent was supplied.\n   - `text`: a short fallback summary (Slack uses it for push notifications and screen-readers).\n   - `blocks`: rich layout with the structured fields.\n   If the call errors or times out, read the channel\u002Fthread history for the message before retrying — a duplicate incident update is worse than a slow one.\n6. **Return the posted message's `ts`** so the next update can thread under it. Save it as a step artifact (e.g. `docs\u002Fincidents\u002F\u003Cid>-slack-thread.ts`).\n7. **Status-page channel mirror** — for sev1\u002Fsev2, 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.\n\n## Output\n\n```text\npost-incident-comms\n\nResolved channel: #inc-2026-09 (id C0XXXXXX)\nParent thread ts: 1716572400.000200\nPosted ts:        1716572734.000300\nMirrored to:      #status-page (one-line summary)\n\nSaved thread root: docs\u002Fincidents\u002F2026-09\u002Fslack-thread.ts\n```\n\n## Quality bar\n\n- Channel ID resolved before posting (not the name).\n- Thread root saved as a step artifact so subsequent updates thread correctly.\n- Status-page channel mirror for sev1\u002Fsev2 (one line, no body duplication).\n- No PII in the fallback `text` field — it appears in push notifications.\n\n## Anti-patterns to avoid\n\n- Calling `chat_postMessage` with the channel name. Some Slack APIs accept it; some don't. Resolve to ID.\n- Re-posting the full update to two channels — duplicate noise. Mirror is one line + a back-pointer.\n- Posting without a thread when one exists. Splits the conversation.\n- Logging the body to plain logs (PII risk). The slack MCP holds it; we don't.\n\n","# post-incident-comms\n\n> 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.\n\n**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.\n\n> **MCP binding (read before any tool call):** if your host has a `slack` MCP 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 as `mcp__claude_ai_\u003CName>__*`). 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.\n\n## When to use\n\n- An incident comms update was drafted by `polymath-incident:comms-update` and needs to go out.\n- A `respondToIncident` workflow step needs to broadcast progress.\n- A status-page-style update is going to the internal channel.\n\n## Inputs\n\n- Update body (required) — or invoke `polymath-incident:comms-update` first to draft one.\n- Incident ID (required) — used to derive the channel name + locate the thread.\n- Channel — explicit (`#inc-2026-09`) or computed from the incident ID. Fall back to `userConfig.defaultIncidentChannel` when neither is supplied.\n- Parent thread `ts` (optional) — when set, the post threads under it. When absent, this update opens a new thread and the returned `ts` becomes the thread root for follow-ups.\n\n## Procedure\n\n1. **Resolve the channel.** Prefer explicit channel input; fall back to `inc-\u003Cincident-id-slug>`; fall back to `userConfig.defaultIncidentChannel`. If none resolves, surface and stop.\n2. **Look up the channel ID** via the slack MCP's `conversations_list` (or `channels.list`). Slack APIs take channel IDs, not names.\n3. **Format the body** — `polymath-incident:comms-update` already produces a status \u002F impact \u002F 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).\n4. **Confirm with the comms lead \u002F 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).\n5. **Post** via the slack MCP's `chat_postMessage` with:\n   - `channel`: resolved ID.\n   - `thread_ts`: if a parent was supplied.\n   - `text`: a short fallback summary (Slack uses it for push notifications and screen-readers).\n   - `blocks`: rich layout with the structured fields.\n   If the call errors or times out, read the channel\u002Fthread history for the message before retrying — a duplicate incident update is worse than a slow one.\n6. **Return the posted message's `ts`** so the next update can thread under it. Save it as a step artifact (e.g. `docs\u002Fincidents\u002F\u003Cid>-slack-thread.ts`).\n7. **Status-page channel mirror** — for sev1\u002Fsev2, 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.\n\n## Output\n\n```text\npost-incident-comms\n\nResolved channel: #inc-2026-09 (id C0XXXXXX)\nParent thread ts: 1716572400.000200\nPosted ts:        1716572734.000300\nMirrored to:      #status-page (one-line summary)\n\nSaved thread root: docs\u002Fincidents\u002F2026-09\u002Fslack-thread.ts\n```\n\n## Quality bar\n\n- Channel ID resolved before posting (not the name).\n- Thread root saved as a step artifact so subsequent updates thread correctly.\n- Status-page channel mirror for sev1\u002Fsev2 (one line, no body duplication).\n- No PII in the fallback `text` field — it appears in push notifications.\n\n## Anti-patterns to avoid\n\n- Calling `chat_postMessage` with the channel name. Some Slack APIs accept it; some don't. Resolve to ID.\n- Re-posting the full update to two channels — duplicate noise. Mirror is one line + a back-pointer.\n- Posting without a thread when one exists. Splits the conversation.\n- Logging the body to plain logs (PII risk). The slack MCP holds it; we don't.\n\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-chat\u002Fskills\u002Fpost-incident-comms","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill post-incident-comms",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill post-incident-comms",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill post-incident-comms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-chat\u002Fskills\u002Fpost-incident-comms\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","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.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","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.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","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).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]