Cyrus Setup Launch

This wraps up Cyrus setup by printing a status summary of your Linear, GitHub, Slack, and repo configuration, then walks you through making it persistent with either pm2 or systemd so it survives reboots. It handles the ngrok start if you configured tunneling, and on macOS or Linux it'll check whether the sandbox CA cert is trusted system-wide, offering to install it if not. The whole point is to get Cyrus running in the background and verify it's listening on localhost before you test it with a real Linear issue or Slack mention. It's careful never to read .env files into context, using only bash commands to check credentials.

skills.sh installs: 223
GitHub stars: 615
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add ceedaragents/cyrus --skill cyrus-setup-launch --agent claude-code

Installs into .claude/skills of the current project.

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.

Setup Launch

Prints a summary of the completed setup and offers to start Cyrus.

Step 1: Gather Configuration

Read current state:

# Base URL
grep '^CYRUS_BASE_URL=' ~/.cyrus/.env 2>/dev/null | cut -d= -f2-

# Linear
grep -c '^LINEAR_CLIENT_ID=' ~/.cyrus/.env 2>/dev/null

# GitHub
gh auth status 2>&1 | head -1

# Slack
grep -c '^SLACK_BOT_TOKEN=' ~/.cyrus/.env 2>/dev/null

# Repositories
cat ~/.cyrus/config.json 2>/dev/null

# Claude auth
grep -c -E '^(ANTHROPIC_API_KEY|CLAUDE_CODE_OAUTH_TOKEN)=' ~/.cyrus/.env 2>/dev/null