메뉴
Add Slack as a channel. Can replace WhatsApp entirely or run alongside it. Uses Socket Mode (no public URL needed).
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SOC 직업 분류 기준
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/b1rdmania/ghostclaw --skill add-slack명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Wire Gmail MCP server into the agent so it can read, search, and send emails. Optional — not core functionality.
Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
| name | add-slack |
| description | Add Slack as a channel. Can replace WhatsApp entirely or run alongside it. Uses Socket Mode (no public URL needed). |
This skill adds Slack support to GhostClaw using the skills engine for deterministic code changes, then walks through interactive setup.
Read .ghostclaw/state.yaml. If slack is in applied_skills, skip to Phase 3 (Setup). The code changes are already in place.
Mode: Replace WhatsApp or add alongside it?
SLACK_ONLY=trueDo they already have a Slack app configured? If yes, collect the Bot Token and App Token now. If no, we'll create one in Phase 3.
Run the skills engine to apply this skill's code package. The package files are in this directory alongside this SKILL.md.
If .ghostclaw/ directory doesn't exist yet:
npx tsx scripts/apply-skill.ts --init
Or call initSkillsSystem() from skills-engine/migrate.ts.
npx tsx scripts/apply-skill.ts .claude/skills/add-slack
This deterministically:
src/channels/slack.ts (SlackChannel class implementing Channel interface)src/channels/slack.test.ts (46 unit tests)src/index.tssrc/config.ts (SLACK_ONLY export)src/routing.test.ts@slack/bolt npm dependency.env.example with SLACK_BOT_TOKEN, SLACK_APP_TOKEN, and SLACK_ONLY.ghostclaw/state.yamlIf the apply reports merge conflicts, read the intent files:
modify/src/index.ts.intent.md — what changed and invariants for index.tsmodify/src/config.ts.intent.md — what changed for config.tsmodify/src/routing.test.ts.intent.md — what changed for routing testsnpm test
npm run build
All tests must pass (including the new slack tests) and build must be clean before proceeding.
If the user doesn't have a Slack app, share SLACK_SETUP.md which has step-by-step instructions with screenshots guidance, troubleshooting, and a token reference table.
Quick summary of what's needed:
xapp-...)message.channels, message.groups, message.imchat:write, channels:history, groups:history, im:history, channels:read, groups:read, users:readxoxb-...)Wait for the user to provide both tokens.
Add to .env:
SLACK_BOT_TOKEN=xoxb-your-bot-token
SLACK_APP_TOKEN=xapp-your-app-token
If they chose to replace WhatsApp:
SLACK_ONLY=true
Sync to container environment:
mkdir -p data/env && cp .env data/env/env
The container reads environment from data/env/env, not .env directly.
npm run build
launchctl kickstart -k gui/$(id -u)/com.ghostclaw
Tell the user:
- Add the bot to a Slack channel (right-click channel → View channel details → Integrations → Add apps)
- In that channel, the channel ID is in the URL when you open it in a browser:
https://app.slack.com/client/T.../C0123456789— theC...part is the channel ID- Alternatively, right-click the channel name → Copy link — the channel ID is the last path segment
The JID format for GhostClaw is:
slack:C0123456789
Wait for the user to provide the channel ID.
Use the IPC register flow or register directly. The channel ID, name, and folder name are needed.
For a main channel (responds to all messages, uses the main folder):
registerGroup("slack:<channel-id>", {
name: "<channel-name>",
folder: "main",
trigger: `@${ASSISTANT_NAME}`,
added_at: new Date().toISOString(),
requiresTrigger: false,
});
For additional channels (trigger-only):
registerGroup("slack:<channel-id>", {
name: "<channel-name>",
folder: "<folder-name>",
trigger: `@${ASSISTANT_NAME}`,
added_at: new Date().toISOString(),
requiresTrigger: true,
});
Tell the user:
Send a message in your registered Slack channel:
- For main channel: Any message works
- For non-main:
@<assistant-name> hello(using the configured trigger word)The bot should respond within a few seconds.
tail -f logs/ghostclaw.log
SLACK_BOT_TOKEN and SLACK_APP_TOKEN are set in .env AND synced to data/env/envsqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'slack:%'"launchctl list | grep ghostclawmessage.channels, message.groups, message.im)By default, bots only see messages in channels they've been explicitly added to. Make sure to:
channels:history and/or groups:history scopesIf the bot logs missing_scope errors:
.envmkdir -p data/env && cp .env data/env/envlaunchctl kickstart -k gui/$(id -u)/com.ghostclawIf the channel ID is hard to find:
C... ID from the URLhttps://app.slack.com/client/TXXXXXXX/C0123456789curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" "https://slack.com/api/conversations.list" | jq '.channels[] | {id, name}'The Slack channel supports:
SLACK_ONLY=true)NewMessage type, Channel.sendMessage interface, and routing logic.setTyping() method is a no-op. Users won't see "bot is typing..." while the agent works.syncChannelMetadata() paginates through all channels the bot is a member of, but has no upper bound or timeout. Workspaces with thousands of channels may experience slow startup.