Skip to content
Get packs

Migrate Classic Slack Agents

Move a single-bot Slack setup to one named Slack app per agent, or stay on classic.

Source Download skill
Repository
nanocoai/nanoclaw
Stars
31,072
Licence
MIT
Files
1 file

What it does

This skill guides an operator through moving a NanoClaw install from one shared Slack bot to a separate, named Slack app for each existing agent group. The agent keeps each group's identity, workspace, memory and routing; it is a step-by-step, resumable data migration rather than a rebuild. It also offers the choice to stay on the classic setup, which the file says remains supported.

Great for

  • Operators of a NanoClaw install who already run several agents through one classic Slack bot and want per-agent Slack identities
  • Maintainers who were prompted by /update-nanoclaw to address the Slack agents requirement and want to decide how to respond
  • Users who prefer to keep classic Slack and only need the acknowledgement recorded

Skip it if

  • People with no NanoClaw installation or no Slack integration, since the skill only operates on existing classic Slack state
  • Anyone who cannot review a dry-run table before changes are made, since the migration touches the central database, environment credentials and Slack app configuration
  • Operators wanting a quick one-command change; the file requires confirmation of the full mapping and staged rollback safeguards

Try asking

  • “Check whether my NanoClaw Slack setup needs the migration to named Slack apps and show me a dry run first.”
  • “Migrate my classic Slack bot to one Slack app per agent group, keeping the existing agent groups and memory.”
  • “I want to stay on classic Slack. Record that decision for the update requirement and leave everything unchanged.”
  • “Resume the Slack agent migration where it stopped and report any partial or inconsistent state.”
Step-by-step guide: how to use Migrate Classic Slack AgentsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    migrate-slack-agents.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip migrate-slack-agents.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip migrate-slack-agents.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Review the dry-run table carefully, including the proposed slugs and any duplicate Slack display names, before approving the mapping.
  • Keep the classic rows, credentials and shared Slack app until you explicitly approve cutover, so you can roll back.
  • Never paste token values into the chat; the skill is designed to show only key names and masked presence.

What's inside

  • SKILL.md

Redistributed unmodified from nanocoai/nanoclaw under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.