What problem does it solve?
NanoClaw installs that use the classic shared Slack bot cannot take advantage of per-agent Slack apps, where each agent gets its own bot identity, avatar, and workspace presence. This Skill performs a guided, resumable migration from the classic single-bot setup to one provisioned Slack app per existing agent group, while preserving agent identities, workspaces, memory, and wiring behavior — or records the operator's decision to stay on classic, which remains fully supported.
Core Features & Use Cases
- State detection and dry-run planning: Detects the classic Slack state via database queries and environment checks, inventories every wired surface (channels, DMs, MPIMs), and presents a full migration map for operator confirmation before any change.
- Per-agent app provisioning: Provisions a named Slack app per agent group using a managed broker or direct Slack manifest API, reuses existing tokens idempotently, and recreates messaging groups and wirings with all recorded behavior fields.
- Verification, cutover, and rollback: Verifies each new bot authenticates and responds without duplicate responders, requires explicit operator approval before cutover, and keeps classic rows and credentials intact as a rollback path.
- Use Case: After running /update-nanoclaw surfaces a breaking Slack agents requirement, an operator runs this Skill to migrate three agent groups from the shared classic bot to individual Slack apps, verifies each bot in its channels, then approves cutover and acknowledges the update requirement.
Quick Start
Ask the assistant to run the migrate-slack-agents skill to move your classic shared Slack bot setup to one provisioned Slack app per agent group.
