cyrus-setup
Skill888 starsChanged 53 days agoApache-2.0View on GitHub
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.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cyrusagents/cyrusword for word, first seen Sep 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cyrusagents/cyrus★ 902100% 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-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- implementationSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
If not, check which agent-browser.
- Very specific: line 30
If neither is available, ask the user: install agent-browser, or follow manual instructions?
- Distinctive: line 68
After connecting, commands work normally:
- Distinctive: line 80
Cleanup: After setup is complete, close the Chrome instance:
- Very specific: line 108
If a sub-skill file is not found, use Glob to search for it: /cyrus-setup-prerequisites/SKILL.md
- Very specific: line 114
Before anything else, collect preferences from the user.
- Distinctive: line 118
Ask the user (defaults in parentheses):
- Distinctive: line 127
Ask the user to select one or more:
- Distinctive: line 138
Ask: npm, pnpm, bun, or yarn?
≈ “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
Cyrus Setup
One-command setup for self-hosted Cyrus. This orchestrator walks you through everything needed to run Claude Code as a background agent from Linear, Slack, and GitHub.
CRITICAL Rules
Never Read or Write ~/.cyrus/.env Directly
FORBIDDEN: Do NOT use Read, Edit, or Write tools on ~/.cyrus/.env or any file inside ~/.cyrus/. This file contains secrets (API keys, tokens, signing secrets). All interaction with this file MUST go through Bash commands (grep, printf >> ..., etc.) which the user can see and approve. Never read its contents into the conversation context.
Browser Automation
The goal of browser automation in this skill is to reduce sign-in and setup fatigue — the agent navigates web UIs, fills forms, and scrapes credentials so the user doesn't have to do it all manually.
Three modes, in order of preference:
claude-in-chrome(preferred when available) — if the user is running Claude Code and has theclaude-in-chromeMCP extension connected, use it. This has the huge advantage of using the user's existing Chrome with all their signed-in sessions (Linear, Slack, GitHub). Check availability by seeing ifmcp__claude-in-chrome__*tools exist.agent-browserCLI — a standalone Playwright-based binary invoked viaBash. Requires launching a fresh Chrome profile with remote debugging enabled (the user will need to sign in to services in that profile). Check withwhich agent-browser.- Manual guided flow — the user follows the agent's step-by-step instructions and does the clicks themselves. Always available as Path B in each sub-skill.
Determining which mode to use:
- First, check if
claude-in-chromeMCP tools are available in the current session. If yes, use those — no setup needed. - If not, check
which agent-browser. If installed, launch a fresh Chrome profile (see below). - If neither is available, ask the user: install
agent-browser, or follow manual instructions?
agent-browser setup — fresh Chrome profile:
agent-browser needs a Chrome instance with remote debugging enabled. Launch one with an isolated profile:
# Find an open port
for port in $(seq 9222 9322); do
if ! lsof -i :"$port" > /dev/null 2>&1; then
echo "Open port found: $port"
break
fi
done# Create a fresh profile directory
mkdir -p ~/.cyrus/chrome-profile# Launch Chrome with remote debugging (runs in background)
# macOS:
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \
--remote-debugging-port=<port> \
--user-data-dir="$HOME/.cyrus/chrome-profile" &
# Linux:
google-chrome --remote-debugging-port=<port> \
--user-data-dir="$HOME/.cyrus/chrome-profile" &# Connect agent-browser to it
agent-browser connect <port>After connecting, commands work normally:
agent-browser navigate "https://example.com"
agent-browser click "button:text('Submit')"
agent-browser fill "#input-id" "value"
agent-browser screenshot
agent-browser eval "document.title"Important: The user will need to sign in to Linear, Slack, and GitHub in this fresh Chrome profile before the agent can automate app creation. The agent should navigate to each service and pause for the user to sign in before proceeding with automation.
Cleanup: After setup is complete, close the Chrome instance:
lsof -ti :<port> | xargs kill 2>/dev/nullHow This Works
This skill runs sub-skills in order, skipping any that are already complete. You can re-run /cyrus-setup at any time to add integrations or fix configuration.
Loading Sub-Skills
Each step references a sub-skill file. To execute a sub-skill, read the SKILL.md file using the Read tool and follow its instructions. The sub-skill files are sibling directories to this skill:
| Step | Sub-skill | File to read |
| 1 | setup-prerequisites | cyrus-setup-prerequisites/SKILL.md (relative to skills directory) |
| 2 | setup-claude-auth | cyrus-setup-claude-auth/SKILL.md |
| 3 | setup-endpoint | cyrus-setup-endpoint/SKILL.md |
| 4 | setup-linear | cyrus-setup-linear/SKILL.md |
| 5 | setup-github | cyrus-setup-github/SKILL.md |
| 5b | setup-gitlab | cyrus-setup-gitlab/SKILL.md |
| 6 | setup-slack | cyrus-setup-slack/SKILL.md |
| 7 | setup-repository | cyrus-setup-repository/SKILL.md |
| 8 | setup-launch | cyrus-setup-launch/SKILL.md |
To find the files, look for them relative to this file's directory (go up one level, then into the sub-skill directory). For example, if this file is at ~/.claude/skills/cyrus-setup/SKILL.md, the sub-skills are at ~/.claude/skills/cyrus-setup-prerequisites/SKILL.md, etc.
If a sub-skill file is not found, use Glob to search for it: **/cyrus-setup-prerequisites/SKILL.md
Step 0: Identity & Surface Selection
Before anything else, collect preferences from the user. Use the AskUserQuestion tool if available — ask questions interactively rather than printing them as a text block. You may bundle related questions into a single ask, or ask them one at a time.
Question 1: Name & Description
Ask the user (defaults in parentheses):
- What would you like to name your agent? — This name appears in Linear, Slack, and GitHub integrations. (default:
Cyrus) - Give your agent a short description — one sentence, shown in integration app listings. (default:
AI coding agent for automated development)
Store as AGENT_NAME and AGENT_DESCRIPTION — used when creating Linear, Slack, and GitHub apps.
Question 2: Which surfaces?
Ask the user to select one or more:
- Linear — issue tracking, recommended for most users
- GitHub — PR comments and issues
- GitLab — MR comments and issues
- Slack — chat messages
At least one is required. Store the selection — it determines which integration sub-skills run (Steps 4-6).
Question 3: Package manager?
Ask: npm, pnpm, bun, or yarn?
Store the answer — used by the prerequisites skill.
Step 1: Prerequisites
Read the cyrus-setup-prerequisites/SKILL.md sub-skill and follow its instructions.
Pass the user's package manager preference from Step 0.
Step 2: Claude Auth
Read the cyrus-setup-claude-auth/SKILL.md sub-skill and follow its instructions.
Step 3: Webhook Endpoint
Read the cyrus-setup-endpoint/SKILL.md sub-skill and follow its instructions.
Step 4: Linear (if selected)
Only if the user selected Linear in Step 0.
Read the cyrus-setup-linear/SKILL.md sub-skill and follow its instructions.
Step 5: GitHub (if selected)
Only if the user selected GitHub in Step 0.
Read the cyrus-setup-github/SKILL.md sub-skill and follow its instructions.
Step 5b: GitLab (if selected)
Only if the user selected GitLab in Step 0.
Read the cyrus-setup-gitlab/SKILL.md sub-skill and follow its instructions.
Step 6: Slack (if selected)
Only if the user selected Slack in Step 0.
Read the cyrus-setup-slack/SKILL.md sub-skill and follow its instructions. All paths (A-1, A-2, and B) must use the manifest-based creation flow — never create the Slack app "from scratch" with manual scope/event configuration.
Step 7: Add Repositories
Read the cyrus-setup-repository/SKILL.md sub-skill and follow its instructions.
Step 8: Launch
Read the cyrus-setup-launch/SKILL.md sub-skill and follow its instructions.
Design Principles
- Skip-if-done — Every sub-skill checks existing state first. Re-running
/setupis safe. - Secrets never enter chat — Credentials are either scraped via agent-browser or written via clipboard-to-env shell commands the user runs in their terminal.
- Agent writes non-secret config — Values like
CYRUS_SERVER_PORTandLINEAR_DIRECT_WEBHOOKSare written directly by the agent. - Browser automation when available — Uses
agent-browserfor Linear/Slack app creation; falls back to guided manual steps if not installed. - Package manager aware — The user's choice is used consistently throughout.
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.

