cyrus-setup-slack
Skill902 starsChanged 53 days agoApache-2.0View on GitHub
Configure Slack integration for Cyrus — create a Slack app from manifest, then guide the user to save credentials.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ceedaragents/cyrusword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ceedaragents/cyrus★ 888100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- release-core-testSkill
- cyrus-setup-claude-authSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-gitlabSkill
- cyrus-setup-launchSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
If SLACK_BOT_TOKEN is already set, inform the user:
- Very specific: line 27
Read the base URL (set by setup-endpoint):
- Distinctive: line 126
All paths use the "From a manifest" flow: Never create the app "From scratch".
- Very specific: line 130
If claude-in-chrome MCP tools are available → use Path A-1 (claude-in-chrome)
- Very specific: line 131
If agent-browser is installed and a Chrome debug session is connected → use Path A-2 (agent-browser)
- Very specific: line 136
Use the mcp__claude-in-chrome__* tools to navigate and interact with the user's existing Chrome browser.
- Distinctive: line 146
After creation, the app lands on the Basic Information page.
- Very specific: line 150
If agent-browser is connected to a Chrome debug session:
- Distinctive: line 194
If that doesn't work, try:
- Distinctive: line 216
After creation, do NOT screenshot credential pages or attempt to scrape secrets.
- Distinctive: line 239
After the app is created (via any path), guide the user through installation and credential collection.
- Distinctive: line 249
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 …
- Distinctive: line 253
Add placeholder lines to the env file so the user can fill them in:
- Distinctive: line 283
After the user confirms they've saved, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/nullIf 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/.env5c. 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/.env5d. 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/.envBoth 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

