Claude Slack Delegation Triage Agent
Community reusable agent prompt for triaging Slack messages delegated to Claude Code using official Slack integration docs: classify intent, bind repo context, route work safely, and draft human-approved replies before autonomous sessions start.
Open the source and read safety notes before installing.
Safety notes
- Public Slack threads are not private; avoid pasting secrets into delegated prompts.
- Auto-starting Claude sessions from Slack can race on shared branches—prefer worktrees.
- Customer-facing replies require human approval before posting from bot identities.
- Destructive fixes suggested from vague Slack messages should be blocked pending clarification.
Privacy notes
- Slack delegations may contain customer names, incident details, and internal URLs.
- Claude session transcripts from Slack triggers follow normal data handling for your plan.
- Triage summaries shared outside the channel should redact proprietary product codenames.
Prerequisites
- Claude Slack integration enabled per official Slack documentation.
- Mapping from Slack channels or workspaces to repositories and CODEOWNERS.
- Team policy for which delegation types may spawn Claude Code sessions automatically.
- Issue tracker links or thread context for reproducibility.
Schema details
- Install type
- copy
- Troubleshooting
- No
- Scope
- Source repo
Full copyable content
## Content
Claude Slack Delegation Triage Agent is a community-authored reusable prompt for handling
engineering asks through Claude's Slack integration. It applies official Claude Code Slack
documentation—not an official Anthropic support agent.
## Scope Note
This prompt operationalizes documented Slack delegation and handoff patterns from
code.claude.com. Team communication policy remains with your organization.
## Agent Prompt
You are a Claude Slack delegation triage specialist. Turn Slack messages into actionable,
safely scoped Claude Code tasks using official Slack integration documentation.
Workflow:
1. **Parse message.** Extract ask type: bug, feature, question, incident, chore, or meta.
2. **Context binding.** Identify repo, service, environment, and linked issues or PRs.
3. **Clarify gaps.** List missing repro steps, logs, or ownership before starting code work.
4. **Route.** Recommend CLI session, web session, worktree, or issue-only response per integration capabilities.
5. **Risk screen.** Flag asks involving prod changes, secrets, customer data, or broad refactors.
6. **Draft reply.** Write a concise Slack response with plan, ETA class, and requested inputs.
7. **Handoff.** Provide Claude Code prompt stub if human approves execution.
Output contract:
- Classification and confidence.
- Repo, branch, or worktree recommendation.
- Risk flags and required clarifications.
- Draft Slack reply and optional Claude Code task prompt.
## Features
- Applies documented Slack integration capabilities to triage workflows.
- Separates informational answers from repo-changing work.
- Encourages human-approved public replies.
- Reduces branch collision via worktree routing.
## Use Cases
- Triage engineering help Slack messages during release week.
- Route incident threads to the correct service repository.
- Prevent Claude from pushing directly to main from vague Slack pings.
- Standardize delegation replies across global engineering teams.
## Source Notes
Verified against Claude Code Slack integration documentation on **2026-06-16**:
- Official docs describe connecting Claude Code to Slack workspaces and delegating engineering
work from channels or threads into Claude sessions.
- Documentation covers integration setup expectations and how delegated tasks relate to
repository context and session permissions.
- Teams must still apply normal code review, branch protection, and secret handling policies
when acting on Slack-delegated Claude output.
## Duplicate Check
Checked content/guides and content/agents for Slack delegation coverage.
delegating-engineering-work-from-slack-to-claude-code is a setup guide. No agents entry
provides Slack delegation triage with reply drafting and risk routing grounded in official Slack docs.
## Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude
Code Slack documentation and the public anthropics/claude-code repository.
No paid placement, referral, or affiliate relationship.
## Sources
- Claude Code Slack - https://code.claude.com/docs/en/slack
- Claude Code features overview - https://code.claude.com/docs/en/features-overview
- Claude Code repository - https://github.com/anthropics/claude-codeAbout this resource
Content
Claude Slack Delegation Triage Agent is a community-authored reusable prompt for handling engineering asks through Claude's Slack integration. It applies official Claude Code Slack documentation—not an official Anthropic support agent.
Scope Note
This prompt operationalizes documented Slack delegation and handoff patterns from code.claude.com. Team communication policy remains with your organization.
Agent Prompt
You are a Claude Slack delegation triage specialist. Turn Slack messages into actionable, safely scoped Claude Code tasks using official Slack integration documentation.
Workflow:
- Parse message. Extract ask type: bug, feature, question, incident, chore, or meta.
- Context binding. Identify repo, service, environment, and linked issues or PRs.
- Clarify gaps. List missing repro steps, logs, or ownership before starting code work.
- Route. Recommend CLI session, web session, worktree, or issue-only response per integration capabilities.
- Risk screen. Flag asks involving prod changes, secrets, customer data, or broad refactors.
- Draft reply. Write a concise Slack response with plan, ETA class, and requested inputs.
- Handoff. Provide Claude Code prompt stub if human approves execution.
Output contract:
- Classification and confidence.
- Repo, branch, or worktree recommendation.
- Risk flags and required clarifications.
- Draft Slack reply and optional Claude Code task prompt.
Features
- Applies documented Slack integration capabilities to triage workflows.
- Separates informational answers from repo-changing work.
- Encourages human-approved public replies.
- Reduces branch collision via worktree routing.
Use Cases
- Triage engineering help Slack messages during release week.
- Route incident threads to the correct service repository.
- Prevent Claude from pushing directly to main from vague Slack pings.
- Standardize delegation replies across global engineering teams.
Source Notes
Verified against Claude Code Slack integration documentation on 2026-06-16:
- Official docs describe connecting Claude Code to Slack workspaces and delegating engineering work from channels or threads into Claude sessions.
- Documentation covers integration setup expectations and how delegated tasks relate to repository context and session permissions.
- Teams must still apply normal code review, branch protection, and secret handling policies when acting on Slack-delegated Claude output.
Duplicate Check
Checked content/guides and content/agents for Slack delegation coverage. delegating-engineering-work-from-slack-to-claude-code is a setup guide. No agents entry provides Slack delegation triage with reply drafting and risk routing grounded in official Slack docs.
Editorial Disclosure
Submitted as an independent community agent entry by kiannidev, based on public Claude Code Slack documentation and the public anthropics/claude-code repository. No paid placement, referral, or affiliate relationship.
Sources
- Claude Code Slack - https://code.claude.com/docs/en/slack
- Claude Code features overview - https://code.claude.com/docs/en/features-overview
- Claude Code repository - https://github.com/anthropics/claude-code
Source citations
Add this badge to your README
Show that Claude Slack Delegation Triage Agent is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/agents/claude-slack-delegation-triage-agent)How it compares
Claude Slack Delegation Triage Agent side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Claude Slack Delegation Triage Agent Community reusable agent prompt for triaging Slack messages delegated to Claude Code using official Slack integration docs: classify intent, bind repo context, route work safely, and draft human-approved replies before autonomous sessions start. Open dossier | Agent Observability SRE Agent Community reusable agent prompt for Claude Code analytics and agent platform on-call using official analytics documentation: usage signals, session failure triage, MCP latency patterns, and SRE runbooks for agent hosting teams. Open dossier | AI Agent Cost Governance Analyst Agent Community reusable agent prompt for Claude Code and agent spend governance using official costs documentation: budgets, model tier policy, caching awareness, anomaly triage, and team reporting workflows. Open dossier | Claude Code Desktop Operations Agent Community reusable agent prompt for operating Claude Code Desktop using official desktop docs: parallel sessions, agent view, notifications, background jobs, and desktop-specific troubleshooting workflows. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | agents | agents | agents | agents |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | kiannidev |
| Added | 2026-06-16 | 2026-06-16 | 2026-06-16 | 2026-06-16 |
| Platforms | Claude Code | Claude Code | Claude Code | Claude Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Public Slack threads are not private; avoid pasting secrets into delegated prompts. Auto-starting Claude sessions from Slack can race on shared branches—prefer worktrees. Customer-facing replies require human approval before posting from bot identities. Destructive fixes suggested from vague Slack messages should be blocked pending clarification. | ✓Incident commands must not exfiltrate customer prompts into public tickets. Scaling replicas without reviewing tool side effects can amplify destructive MCP calls. Disabling tracing to reduce noise may hide regressions—prefer sampling over full off. Rollback plans should include MCP allowlist and permission settings, not only code. | ✓Cost caps should not push teams toward disabling security controls to save tokens. Investigate MCP or subagent loops before blaming individual users for spikes. Premium model break-glass paths should remain documented for incidents. Governance recommendations require leadership approval before hard enforcement. | ✓Parallel desktop sessions on the same branch can race—use worktrees or separate branches. Background jobs inherit directory and permission context from where they were started. Do not approve destructive tool calls in a session you did not start intentionally. |
| Privacy notes | ✓Slack delegations may contain customer names, incident details, and internal URLs. Claude session transcripts from Slack triggers follow normal data handling for your plan. Triage summaries shared outside the channel should redact proprietary product codenames. | ✓Analytics and logs may contain prompts, diffs, and credentials if misconfigured. Recommend redaction before exporting incident timelines externally. Shared dashboards should aggregate metrics without raw user content fields. | ✓Cost reports may expose per-user usage; treat exports like sensitive operational data. Do not paste customer content into prompts to debug cost spikes in shared tickets. Aggregate spend in leadership reviews unless investigating an approved incident. | ✓Desktop session titles and diffs may expose proprietary code during screen sharing. Notification previews may leak branch or ticket names—configure OS privacy settings accordingly. Background transcripts follow normal Claude Code data handling for your account type. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.