incident-comms

Reads Slack channels and posts incident status updates via bot-authenticated API scripts.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill incident-comms-erwinv2k-tkg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incident-comms
Source: https://github.com/erwinv2k-TKG/AgentesVSC/tree/main/packs/incidentfox/sre-agent/.claude/skills/incident-comms
Command: npx skills add https://github.com/erwinv2k-TKG/AgentesVSC --skill incident-comms-erwinv2k-tkg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) components.

What problem does it solve? During an incident, responders need to gather context from Slack channels and keep stakeholders informed, but manually searching channels and writing updates slows down the response. This Skill automates reading incident channels, threads, and posting structured status updates through the Slack API. ## Core Features & Use Cases - Channel Discovery and Reading: List channels the bot can access, filter by name, read channel history, and expand thread replies to build incident context. - Status Update Posting: Post investigation updates, root cause summaries, and resolution notices to channels or threads using ready-made templates. - Bot-Token Workflow: Works within bot token permissions, replacing unavailable message search with a channel-scanning workflow. - Use Case: When an alert fires, list incident-related channels, read recent history and threads to understand prior discussion, then post a structured "Investigation Started" update in the incident thread. ## Quick Start Use the incident-comms skill to find recent discussion in our incident channels and post an investigation started update to the active incident thread.

Frequently Asked Questions about incident-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read Slack channel history with a bot token?

Use the get_channel_history.py script with a channel ID to call the conversations.history endpoint. The bot must be a member of the channel, which you can verify with list_channels.py where member channels are marked with a star.

How do I post incident status updates to a Slack thread?

Run post_message.py with the channel ID, message text, and the thread timestamp. The script calls chat.postMessage with the thread_ts parameter so the update appears as a reply inside the incident thread.

Why does Slack message search fail with a bot token?

The search.messages endpoint requires a user token, so bot tokens receive a missing_scope error. The recommended workaround is scanning channels directly: list channels, read their history, and expand relevant threads.

Can a Slack bot read channels it has not joined?

No. A bot can only read history from channels where it is a member. Use list_channels.py to see which channels show the membership marker before attempting to read their history.

Where does the Slack bot token come from in these scripts?

Credentials are injected automatically by the IncidentFox credential proxy, so scripts do not read SLACK_BOT_TOKEN from the environment in production. For local development, a direct token and the standard slack.com API base URL are used as a fallback.