[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H3RYQZA504TF3PJ5MRCPD0":3,"skill-same:01M6H3RYQZA504TF3PJ5MRCPD0":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":63},"01M6H3RYQZA504TF3PJ5MRCPD0","add-slack",null,"Add Slack as a channel. Can replace WhatsApp entirely or run alongside it. Uses Socket Mode (no public URL needed).","sliamh11\u002FDeus","sliamh11","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68326628?v=4","01M6H3PPFXQ6C98QV1RJA5W72S","Liam Steiner","01M6H3PPM81GJC6KYCNTY9A3AT",51,"MIT","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadd-slack\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"slack","add slack","add","whatsapp","run","public","channel","as","it","URL","true","can","mode","socket","2026-11-10 10:12:30",false,"---\nname: add-slack\ndescription: Add Slack as a channel. Can replace WhatsApp entirely or run alongside it. Uses Socket Mode (no public URL needed).\ndisable-model-invocation: true\n---\n\n# Add Slack Channel\n\n> **Status:** Coming soon — this channel will be available as `@deus-ai\u002Fslack-mcp`. The MCP package is not yet available.\n\nThis skill will add Slack support to Deus once the MCP package is released. In the meantime, the setup\u002Fconfig\u002Fregistration phases below describe what the integration will look like.\n\n## Phase 1: Setup (Future)\n\n### Create Slack App (if needed)\n\nIf the user doesn't have a Slack app, share [SLACK_SETUP.md](SLACK_SETUP.md) which has step-by-step instructions with screenshots guidance, troubleshooting, and a token reference table.\n\nQuick summary of what's needed:\n1. Create a Slack app at [api.slack.com\u002Fapps](https:\u002F\u002Fapi.slack.com\u002Fapps)\n2. Enable Socket Mode and generate an App-Level Token (`xapp-...`)\n3. Subscribe to bot events: `message.channels`, `message.groups`, `message.im`\n4. Add OAuth scopes: `chat:write`, `channels:history`, `groups:history`, `im:history`, `channels:read`, `groups:read`, `users:read`\n5. Install to workspace and copy the Bot Token (`xoxb-...`)\n\n### Configure environment\n\nAdd to `.env`:\n\n```bash\nSLACK_BOT_TOKEN=xoxb-your-bot-token\nSLACK_APP_TOKEN=xapp-your-app-token\n```\n\nChannels auto-enable when their credentials are present — no extra configuration needed.\n\nSync to container environment:\n\n```bash\nmkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv\n```\n\nThe container reads environment from `data\u002Fenv\u002Fenv`, not `.env` directly.\n\n## Phase 2: Registration (Future)\n\n### Get Channel ID\n\nTell the user:\n\n> 1. Add the bot to a Slack channel (right-click channel → **View channel details** → **Integrations** → **Add apps**)\n> 2. In that channel, the channel ID is in the URL when you open it in a browser: `https:\u002F\u002Fapp.slack.com\u002Fclient\u002FT...\u002FC0123456789` — the `C...` part is the channel ID\n> 3. Alternatively, right-click the channel name → **Copy link** — the channel ID is the last path segment\n>\n> The JID format for Deus is: `slack:C0123456789`\n\n### Register the channel\n\nThe channel ID, name, and folder name are needed. Use `npx tsx setup\u002Findex.ts --step register` with the appropriate flags.\n\nFor a main channel (responds to all messages):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"slack:\u003Cchannel-id>\" --name \"\u003Cchannel-name>\" --folder \"slack_main\" --trigger \"@${ASSISTANT_NAME}\" --channel slack --no-trigger-required --is-main\n```\n\nFor additional channels (trigger-only):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"slack:\u003Cchannel-id>\" --name \"\u003Cchannel-name>\" --folder \"slack_\u003Cchannel-name>\" --trigger \"@${ASSISTANT_NAME}\" --channel slack\n```\n\n## Verify\n\n### Smoke test\n\nRun the automated smoke test to verify service, DB, and channel connection:\n\n```bash\nnpx tsx setup\u002Findex.ts --step smoke-test -- --channel slack\n```\n\nThe smoke test checks: service running, registered group exists, DB write\u002Fread works, and channel connection appears in logs.\n\nIf the smoke test passes, tell the user \"Slack channel is working.\"\n\nIf it fails, check the STATUS output for the specific failure (service down, no registered group, DB error, or no log connection). Guide the user to fix the issue before proceeding.\n\nAfter the automated check, also ask the user to send a test message to verify real-time delivery:\n\n> Send a message in your registered Slack channel to confirm real-time delivery.\n> - For main channel: Any message works\n> - For non-main: @mention the bot\n\n## Troubleshooting\n\n### Bot not responding\n\n1. Check `SLACK_BOT_TOKEN` and `SLACK_APP_TOKEN` are set in `.env` AND synced to `data\u002Fenv\u002Fenv`\n2. Check channel is registered: `sqlite3 store\u002Fmessages.db \"SELECT * FROM registered_groups WHERE jid LIKE 'slack:%'\"`\n3. For non-main channels: message must include trigger pattern\n4. Service is running: `launchctl list | grep deus`\n\n### Bot connected but not receiving messages\n\n1. Verify Socket Mode is enabled in the Slack app settings\n2. Verify the bot is subscribed to the correct events (`message.channels`, `message.groups`, `message.im`)\n3. Verify the bot has been added to the channel\n4. Check that the bot has the required OAuth scopes\n\n### Bot not seeing messages in channels\n\nBy default, bots only see messages in channels they've been explicitly added to. Make sure to:\n1. Add the bot to each channel you want it to monitor\n2. Check the bot has `channels:history` and\u002For `groups:history` scopes\n\n### \"missing_scope\" errors\n\nIf the bot logs `missing_scope` errors:\n1. Go to **OAuth & Permissions** in your Slack app settings\n2. Add the missing scope listed in the error message\n3. **Reinstall the app** to your workspace — scope changes require reinstallation\n4. Copy the new Bot Token (it changes on reinstall) and update `.env`\n5. Sync: `mkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv`\n6. Restart: `launchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus`\n\n### Getting channel ID\n\nIf the channel ID is hard to find:\n- In Slack desktop: right-click channel → **Copy link** → extract the `C...` ID from the URL\n- In Slack web: the URL shows `https:\u002F\u002Fapp.slack.com\u002Fclient\u002FTXXXXXXX\u002FC0123456789`\n- Via API: `curl -s -H \"Authorization: Bearer $SLACK_BOT_TOKEN\" \"https:\u002F\u002Fslack.com\u002Fapi\u002Fconversations.list\" | jq '.channels[] | {id, name}'`\n\n## After Setup\n\nThe Slack channel supports:\n- **Public channels** — Bot must be added to the channel\n- **Private channels** — Bot must be invited to the channel\n- **Direct messages** — Users can DM the bot directly\n- **Multi-channel** — Can run alongside WhatsApp or other channels (auto-enabled by credentials)\n\n## Known Limitations\n\n- **Threads are flattened** — Threaded replies are delivered to the agent as regular channel messages. The agent sees them but has no awareness they originated in a thread. Responses always go to the channel, not back into the thread. Users in a thread will need to check the main channel for the bot's reply. Full thread-aware routing (respond in-thread) requires pipeline-wide changes: database schema, `NewMessage` type, `Channel.sendMessage` interface, and routing logic.\n- **No typing indicator** — Slack's Bot API does not expose a typing indicator endpoint. The `setTyping()` method is a no-op. Users won't see \"bot is typing...\" while the agent works.\n- **Message splitting is naive** — Long messages are split at a fixed 4000-character boundary, which may break mid-word or mid-sentence. A smarter split (on paragraph or sentence boundaries) would improve readability.\n- **No file\u002Fimage handling** — The bot only processes text content. File uploads, images, and rich message blocks are not forwarded to the agent.\n- **Channel metadata sync is unbounded** — `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.\n- **Workspace admin policies not detected** — If the Slack workspace restricts bot app installation, the setup will fail at the \"Install to Workspace\" step with no programmatic detection or guidance. See SLACK_SETUP.md troubleshooting section.\n","# Add Slack Channel\n\n> **Status:** Coming soon — this channel will be available as `@deus-ai\u002Fslack-mcp`. The MCP package is not yet available.\n\nThis skill will add Slack support to Deus once the MCP package is released. In the meantime, the setup\u002Fconfig\u002Fregistration phases below describe what the integration will look like.\n\n## Phase 1: Setup (Future)\n\n### Create Slack App (if needed)\n\nIf the user doesn't have a Slack app, share [SLACK_SETUP.md](SLACK_SETUP.md) which has step-by-step instructions with screenshots guidance, troubleshooting, and a token reference table.\n\nQuick summary of what's needed:\n1. Create a Slack app at [api.slack.com\u002Fapps](https:\u002F\u002Fapi.slack.com\u002Fapps)\n2. Enable Socket Mode and generate an App-Level Token (`xapp-...`)\n3. Subscribe to bot events: `message.channels`, `message.groups`, `message.im`\n4. Add OAuth scopes: `chat:write`, `channels:history`, `groups:history`, `im:history`, `channels:read`, `groups:read`, `users:read`\n5. Install to workspace and copy the Bot Token (`xoxb-...`)\n\n### Configure environment\n\nAdd to `.env`:\n\n```bash\nSLACK_BOT_TOKEN=xoxb-your-bot-token\nSLACK_APP_TOKEN=xapp-your-app-token\n```\n\nChannels auto-enable when their credentials are present — no extra configuration needed.\n\nSync to container environment:\n\n```bash\nmkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv\n```\n\nThe container reads environment from `data\u002Fenv\u002Fenv`, not `.env` directly.\n\n## Phase 2: Registration (Future)\n\n### Get Channel ID\n\nTell the user:\n\n> 1. Add the bot to a Slack channel (right-click channel → **View channel details** → **Integrations** → **Add apps**)\n> 2. In that channel, the channel ID is in the URL when you open it in a browser: `https:\u002F\u002Fapp.slack.com\u002Fclient\u002FT...\u002FC0123456789` — the `C...` part is the channel ID\n> 3. Alternatively, right-click the channel name → **Copy link** — the channel ID is the last path segment\n>\n> The JID format for Deus is: `slack:C0123456789`\n\n### Register the channel\n\nThe channel ID, name, and folder name are needed. Use `npx tsx setup\u002Findex.ts --step register` with the appropriate flags.\n\nFor a main channel (responds to all messages):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"slack:\u003Cchannel-id>\" --name \"\u003Cchannel-name>\" --folder \"slack_main\" --trigger \"@${ASSISTANT_NAME}\" --channel slack --no-trigger-required --is-main\n```\n\nFor additional channels (trigger-only):\n\n```bash\nnpx tsx setup\u002Findex.ts --step register -- --jid \"slack:\u003Cchannel-id>\" --name \"\u003Cchannel-name>\" --folder \"slack_\u003Cchannel-name>\" --trigger \"@${ASSISTANT_NAME}\" --channel slack\n```\n\n## Verify\n\n### Smoke test\n\nRun the automated smoke test to verify service, DB, and channel connection:\n\n```bash\nnpx tsx setup\u002Findex.ts --step smoke-test -- --channel slack\n```\n\nThe smoke test checks: service running, registered group exists, DB write\u002Fread works, and channel connection appears in logs.\n\nIf the smoke test passes, tell the user \"Slack channel is working.\"\n\nIf it fails, check the STATUS output for the specific failure (service down, no registered group, DB error, or no log connection). Guide the user to fix the issue before proceeding.\n\nAfter the automated check, also ask the user to send a test message to verify real-time delivery:\n\n> Send a message in your registered Slack channel to confirm real-time delivery.\n> - For main channel: Any message works\n> - For non-main: @mention the bot\n\n## Troubleshooting\n\n### Bot not responding\n\n1. Check `SLACK_BOT_TOKEN` and `SLACK_APP_TOKEN` are set in `.env` AND synced to `data\u002Fenv\u002Fenv`\n2. Check channel is registered: `sqlite3 store\u002Fmessages.db \"SELECT * FROM registered_groups WHERE jid LIKE 'slack:%'\"`\n3. For non-main channels: message must include trigger pattern\n4. Service is running: `launchctl list | grep deus`\n\n### Bot connected but not receiving messages\n\n1. Verify Socket Mode is enabled in the Slack app settings\n2. Verify the bot is subscribed to the correct events (`message.channels`, `message.groups`, `message.im`)\n3. Verify the bot has been added to the channel\n4. Check that the bot has the required OAuth scopes\n\n### Bot not seeing messages in channels\n\nBy default, bots only see messages in channels they've been explicitly added to. Make sure to:\n1. Add the bot to each channel you want it to monitor\n2. Check the bot has `channels:history` and\u002For `groups:history` scopes\n\n### \"missing_scope\" errors\n\nIf the bot logs `missing_scope` errors:\n1. Go to **OAuth & Permissions** in your Slack app settings\n2. Add the missing scope listed in the error message\n3. **Reinstall the app** to your workspace — scope changes require reinstallation\n4. Copy the new Bot Token (it changes on reinstall) and update `.env`\n5. Sync: `mkdir -p data\u002Fenv && cp .env data\u002Fenv\u002Fenv`\n6. Restart: `launchctl kickstart -k gui\u002F$(id -u)\u002Fcom.deus`\n\n### Getting channel ID\n\nIf the channel ID is hard to find:\n- In Slack desktop: right-click channel → **Copy link** → extract the `C...` ID from the URL\n- In Slack web: the URL shows `https:\u002F\u002Fapp.slack.com\u002Fclient\u002FTXXXXXXX\u002FC0123456789`\n- Via API: `curl -s -H \"Authorization: Bearer $SLACK_BOT_TOKEN\" \"https:\u002F\u002Fslack.com\u002Fapi\u002Fconversations.list\" | jq '.channels[] | {id, name}'`\n\n## After Setup\n\nThe Slack channel supports:\n- **Public channels** — Bot must be added to the channel\n- **Private channels** — Bot must be invited to the channel\n- **Direct messages** — Users can DM the bot directly\n- **Multi-channel** — Can run alongside WhatsApp or other channels (auto-enabled by credentials)\n\n## Known Limitations\n\n- **Threads are flattened** — Threaded replies are delivered to the agent as regular channel messages. The agent sees them but has no awareness they originated in a thread. Responses always go to the channel, not back into the thread. Users in a thread will need to check the main channel for the bot's reply. Full thread-aware routing (respond in-thread) requires pipeline-wide changes: database schema, `NewMessage` type, `Channel.sendMessage` interface, and routing logic.\n- **No typing indicator** — Slack's Bot API does not expose a typing indicator endpoint. The `setTyping()` method is a no-op. Users won't see \"bot is typing...\" while the agent works.\n- **Message splitting is naive** — Long messages are split at a fixed 4000-character boundary, which may break mid-word or mid-sentence. A smarter split (on paragraph or sentence boundaries) would improve readability.\n- **No file\u002Fimage handling** — The bot only processes text content. File uploads, images, and rich message blocks are not forwarded to the agent.\n- **Channel metadata sync is unbounded** — `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.\n- **Workspace admin policies not detected** — If the Slack workspace restricts bot app installation, the setup will fail at the \"Install to Workspace\" step with no programmatic detection or guidance. See SLACK_SETUP.md troubleshooting section.\n",{"name":5,"description":7,"disable-model-invocation":43},true,"main","2f24c38a2ae42d3161492f0729975b286452f4b4",".claude\u002Fskills\u002Fadd-slack",7,"https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus","https:\u002F\u002Fgithub.com\u002Fsliamh11","2026-11-13 20:39:27",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":43},[53,56,59],{"tool":54,"command":55},"npx","npx skills add sliamh11\u002FDeus --skill add-slack",{"tool":57,"command":58},"bunx","bunx skills add sliamh11\u002FDeus --skill add-slack",{"tool":60,"command":61},"pnpm","pnpm dlx skills add sliamh11\u002FDeus --skill add-slack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadd-slack\u002FSKILL.md",[],[65,91,111,125,135,149],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":38},"01M6H3ZC87AJDM8566RP3CQ6BF","status","Quick read-only health check — session context, workspace mounts, tool availability, and task snapshot. Use when the user asks for system status or runs \u002Fstatus.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fstatus\u002FSKILL.md",[],[67,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90],"health","snapshot","for","read-only","quick","availability","session context","task","health check","only","use","session","user","context","read","check","workspace","tool","system",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":102,"publishedAt":38},"01M6H3Z8SK38PVH2B0W7NBP6ZP","resume","Load context from permanent memory and recent session logs. Tiered loading — CLAUDE.md full, session logs frontmatter-only by default.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fresume\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[93,103,104,105,106,107,108,81,83,85,109,110],"memory","load","loading","full","session logs","default","logs","frontmatter",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":38},"01M6H3Z56ZBPKX77THMWSSHZCW","preserve","Scan the current conversation and silently save anything worth permanent memory to CLAUDE.md. Keeps the file compact — structured key:value, no prose.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fpreserve\u002FSKILL.md",[],[113,118,119,120,121,122,123,124,103],"structured","compact","scan","conversation","prose","save","file",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":38},"01M6H3Z1AKK58CWWY762YD3X9A","compress","Save the current session to the vault. Writes a compact session log with a TL;DR frontmatter (always) and full details below (when useful).","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fcompress\u002FSKILL.md",[],[127,132,110,106,119,133,83,123,134],"with","log","vault",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":38},"01M6H3YX6STE1ZJC06EKWMY0M6","capabilities","Show what this Deus instance can do — installed skills, available tools, and system info. Read-only. Use when the user asks what the bot can do, what's installed, or runs \u002Fcapabilities.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fcapabilities\u002FSKILL.md",[],[137,142,143,90,75,35,144,145,146,147,148,81,82,84,86],"Tools","bot","system info","info","what the","do","show",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":38},"01M6H3YSNXYAR7NC1TZPFCANZN","agent-browser","Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.","https:\u002F\u002Fgithub.com\u002Fsliamh11\u002FDeus\u002Fblob\u002Fmain\u002Fcontainer\u002Fskills\u002Fagent-browser\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[159,160,161,74,132,162,163,164,79,165,82,86,166,167,168,169,170,171,172,173],"agent browser","browser","take","apps","pages","forms","test web","just","Bash","browse","data","web","test","research","screenshots"]