Slack Ecosystem
Slack is the team-communication route when the task involves channels, messages, internal status, search, or drafting/sending team updates. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27
When To Use This
Use Slack when the work is communication state: find messages, summarize channels, draft replies, or send internal updates. Use Linear for task state and GitHub for code state. Source: Skill Resolver, 2026-06-27
Decision Matrix
| Need | Route | Verification |
|---|---|---|
| Read/search messages | Slack MCP | Channel/thread/message IDs |
| Browser-only workflow | Browser Testing Skills skill | Screenshot or message link |
| Internal wording | Writing and Content Skills | Draft in Kevin's voice |
| Send message | Slack MCP or skill after approval | Sent message link |
Core Model
Slack is conversation context, not durable project memory. Summaries that matter should be promoted into wiki pages, issues, or docs after the Slack operation. Source: Memory Routing Protocol, 2026-06-27
Claude Tag is the exception-shaped product surface to track: Slack becomes a shared agent workspace when Claude has channel-scoped memory, selected tools/data/codebase access, and explicit admin controls. Even then, Slack remains a collaboration surface; durable decisions and outputs still need to land in the right system of record. Source: Anthropic, 2026-06-23
Routing Summary
Preferred order: Slack MCP for messages/channels/search, Browser Testing Skills for browser-based automation, Writing and Content Skills for internal wording. Ask before sending or posting. Source: Skill Resolver, 2026-06-27
Failure Modes
- Treating Slack messages as durable source of truth without compiling them.
- Sending before user approval.
- Losing channel/thread context.
- Confusing private/team comms with public writing voice.
Verification Path
For reads, return channel, thread, timestamp, and summary. For writes, ask before send and then return the message URL or timestamp. Source: Skill Resolver, 2026-06-27
Timeline
- 2026-07-04 | Linked Claude Tag as the Slack-native shared-agent surface while preserving the memory-routing rule: important outputs should still compile into durable docs, issues, or wiki pages. Source: Anthropic, 2026-06-23
- 2026-06-27 | Canonical ecosystem page created so Slack has product-level routing distinct from the Slack executable skills. Source: User request, 2026-06-27; Ecosystem Capability Coverage