
cyrus-setup-slack
Configure Slack integration for Cyrus — create a Slack app from manifest, then guide the user to save credentials.
- Installs
- 907
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/cyrusagents/cyrus --skill cyrus-setup-slack- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads cyrus-setup-slack automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
CRITICAL: Never use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. Use only Bash commands (grep, printf >>, etc.) to interact with env files — secrets must never be read into the conversation context. Never scrape, extract, or read secret values from web pages — guide the user to copy them manually.
Setup Slack
Creates a Slack application from a pre-built manifest so Cyrus can respond to messages in Slack channels.
Step 1: Check Existing Configuration
grep -E '^SLACK_BOT_TOKEN=' ~/.cyrus/.env 2>/dev/null
If SLACK_BOT_TOKEN is already set, inform the user:
Slack is already configured. Skipping this step. To reconfigure, remove
SLACK_BOT_TOKENandSLACK_SIGNING_SECRETfrom~/.cyrus/.envand re-run.
Skip to completion.
Step 2: Read Variables
Read the base URL (set by setup-endpoint):
grep '^CYRUS_BASE_URL=' ~/.cyrus/.env | cut -d= -f2-
You also need AGENT_NAME and AGENT_DESCRIPTION — these were collected in Step 0 of the orchestrator and should be available from the conversation context.
Step 3: Build Manifest JSON
Construct the manifest, substituting <AGENT_NAME>, <AGENT_DESCRIPTION>, and <CYRUS_BASE_URL> with actual values.
IMPORTANT: Use the manifest template EXACTLY as shown below. The event subscription path MUST be /slack-webhook (not /slack/events or any other path). This matches the route registered by SlackEventTransport in the Cyrus codebase.
NOTE: this list of scopes must be kept in sync with the Slack App configuration and the list of scopes defined at https://github.com/cyrusagents/cyrus-hosted/blob/main/apps/app/src/lib/slack/constants.ts. If you change scopes here, propose matching changes there and update any live Slack App configuration that relies on this manifest.
{
"display_information": {
"name": "<AGENT_NAME>",
"description": "<AGENT_DESCRIPTION>",
"background_color": "#00240e"
},
"features": {
"bot_user": {
"display_name": "<AGENT_NAME>",
"always_online": true
}
},
"oauth_config": {
"redirect_urls": [
"<CYRUS_BASE_URL>/slack/oauth/callback"
],
"scopes": {
"user": [
"canvases:read",
"canvases:write",
"channels:history",
"chat:write",
"groups:history",
"im:history",
"mpim:history",
"users:read",
"users:read.email",
"reactions:write",
"search:read.public",
"search:read.private",
"search:read.mpim",
"search:read.im",
"search:read.files",
"search:read.users"
],
"bot": [
"groups:read",
"app_mentions:read",
"assistant:write",
"canvases:write",
"channels:history",
"channels:read",
"chat:write",
"chat:write.customize",
"groups:history",
"im:history",
"im:read",
"files:read",
"files:write",
"mpim:history",
"reactions:write",
"search:read.files",
"search:read.public",
"search:read.users",
"users:read",
"users:read.email",
"mpim:read"
]
},
"pkce_enabled": false
},
"settings": {
"event_subscriptions": {
"request_url": "<CYRUS_BASE_URL>/slack-webhook",
"bot_events": [
"app_mention",
"member_joined_channel",
"message.channels",
"message.groups",
"message.mpim",
"message.im"
]
},
"org_deploy_enabled": false,
"socket_mode_enabled": false,
"token_rotation_enabled": false
}
}
Step 4: Create Slack App
All paths use the "From a manifest" flow. Never create the app "From scratch".
Determine which browser automation mode to use (see orchestrator rules):
- If
claude-in-chromeMCP tools are available → use Path A-1 (claude-in-chrome) - If
agent-browseris installed and a Chrome debug session is connected → use Path A-2 (agent-browser) - Otherwise → use Path B (manual)
Path A-1: claude-in-chrome Automation
Use the mcp__claude-in-chrome__* tools to navigate and interact with the user's existing Chrome browser.
- Navigate to https://api.slack.com/apps
- Click Create New App
- Select From a manifest in the modal
- Pick the workspace
- Click Next
- Select JSON tab and paste the manifest from Step 3 (fully substituted with real values)
- Click Next, review, click Create
After creation, the app lands on the Basic Information page. Do NOT take screenshots of credential pages. Proceed to Step 5 (credential collection).
Path A-2: agent-browser Automation
If agent-browser is connected to a Chrome debug session:
4a. Navigate to Slack app creation
agent-browser navigate "https://api.slack.com/apps"
Take a screenshot to verify the page loaded and the user is logged in.
4b. Click "Create New App"
agent-browser click "button:text('Create New App')"
4c. Select "From a manifest" in the modal
agent-browser click "button:text('From a manifest')"
4d. Select workspace
Take a screenshot to see the workspace picker. Click the appropriate workspace. If multiple are listed, ask the user which one.
agent-browser click "button:text('Next')"
4e. Select JSON format and paste manifest
Click the JSON tab if not already selected:
agent-browser click "button:text('JSON')"
Paste the manifest using JavaScript:
agent-browser eval "var editor = document.querySelector('textarea, [role=\"textbox\"], .ace_editor textarea, .CodeMirror textarea'); if (editor) { var nativeInputValueSetter = Object.getOwnPropertyDescriptor(window.HTMLTextAreaElement.prototype, 'value').set; nativeInputValueSetter.call(editor, JSON.stringify(<MANIFEST_JSON>, null, 2)); editor.dispatchEvent(new Event('input', { bubbles: true })); 'pasted'; } else { 'editor not found'; }"
If that doesn't work, try:
agent-browser click "textarea"
agent-browser keyboard "Control+a"
agent-browser type '<MANIFEST_JSON_STRING>'
Take a screenshot to verify, then click Next:
agent-browser click "button:text('Next')"
4f. Review and create
Take a screenshot to verify the summary, then click Create:
agent-browser click "button:text('Create')"
After creation, do NOT screenshot credential pages or attempt to scrape secrets. Proceed to Step 5.
Path B: Manual Guided Setup
Guide the user through the manifest flow:
Create a Slack App
- Go to https://api.slack.com/apps
- Click Create New App
- In the modal, select From a manifest
- Pick the workspace you want to associate the app with
- Click Next
- Select JSON format and paste the following manifest:
Print the fully-substituted manifest JSON for the user to copy.
- Click Next, review the summary, then click Create
Proceed to Step 5.
Step 5: Install App & Collect Credentials
After the app is created (via any path), guide the user through installation and credential collection. The agent must NOT scrape, read, or extract secrets from the page. The user copies them manually.
5a. Install to Workspace
Tell the user:
- In your Slack app settings, go to Install App in the left sidebar
- Click Install to Workspace
- Click Allow
If using browser automation (A-1 or A-2), the agent can navigate to the Install App page and click the buttons — but must stop after installation completes and not screenshot the resulting page.
5b. Add Credential Placeholders
Add placeholder lines to the env file so the user can fill them in:
grep -q '^SLACK_BOT_TOKEN=' ~/.cyrus/.env || echo 'SLACK_BOT_TOKEN=' >> ~/.cyrus/.env
grep -q '^SLACK_SIGNING_SECRET=' ~/.cyrus/.env || echo 'SLACK_SIGNING_SECRET=' >> ~/.cyrus/.env
5c. Open env file for editing
# macOS
code --new-window ~/.cyrus/.env 2>/dev/null || open -a TextEdit ~/.cyrus/.env
# Linux
code --new-window ~/.cyrus/.env 2>/dev/null || xdg-open ~/.cyrus/.env
5d. Guide the user to copy credentials
Tell the user:
I've opened
~/.cyrus/.env. You need to paste two values:
Bot User OAuth Token — go to your app's OAuth & Permissions page, copy the Bot User OAuth Token (starts with
xoxb-), and paste it afterSLACK_BOT_TOKEN=Signing Secret — go to your app's Basic Information page, scroll to App Credentials, click Show next to Signing Secret, copy it, and paste it after
SLACK_SIGNING_SECRET=Save and close the file when done.
5e. Wait and verify
After the user confirms they've saved, verify:
grep -c '^SLACK_BOT_TOKEN=.' ~/.cyrus/.env
grep -c '^SLACK_SIGNING_SECRET=.' ~/.cyrus/.env
Both must return 1 (the . after = ensures the value is not empty). If either is 0, ask the user to check the file.
Completion
✓ Slack app created from manifest and installed ✓ Bot token and signing secret saved to
~/.cyrus/.env
Note: The event subscription request_url will fail Slack's verification challenge until Cyrus is actually running. Once Cyrus is started, go to the app's Event Subscriptions page and re-enter the URL to trigger verification, or Slack will retry automatically.
FAQ
What does the cyrus-setup-slack skill do?
Configure Slack integration for Cyrus — create a Slack app from manifest, then guide the user to save credentials.
How do I install cyrus-setup-slack?
Run npx skills add https://github.com/cyrusagents/cyrus --skill cyrus-setup-slack in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cyrus-setup-slack/ (personal) or .claude/skills/cyrus-setup-slack/ (project).
Which AI agents can use cyrus-setup-slack?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is cyrus-setup-slack safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains cyrus-setup-slack?
It is published by cyrusagents in cyrusagents/cyrus. It has 907 recorded installs.
More from cyrusagents/cyrus
cyrus-setup
cyrusagents/cyrus
Set up Cyrus end-to-end — install prerequisites, configure authentication, create integrations (Linear, GitHub, Slack), add repositories, and launch. Run this once to get Cyrus running as a background agent.
cyrus-setup-linear
cyrusagents/cyrus
Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.
cyrus-setup-claude-auth
cyrusagents/cyrus
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
cyrus-setup-github
cyrusagents/cyrus
Configure GitHub for Cyrus — gh CLI login and git config for PRs, with optional webhook setup to enable @mention responses in PR comments, automated rebases and merges, and auto-fixing based on CI failures (coming soon).
cyrus-setup-prerequisites
cyrusagents/cyrus
Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package.
cyrus-setup-endpoint
cyrusagents/cyrus
Configure the public webhook endpoint for Cyrus — ngrok, Cloudflare Tunnel, or custom URL.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。