cyrus-setup-prerequisites
Skill902 starsChanged 53 days agoApache-2.0View on GitHub
Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package.
- Reads credentials
- Installs packages
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-repositorySkill
- cyrus-setupSkill
- 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, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If the user hasn't already specified their preferred package manager, ask:
- Distinctive: line 22
Run the following checks and report results:
- Distinctive: line 43
If all dependencies are present, print a checkmark for each and continue.
- Very specific: line 45
If any are missing, offer to install them (detect OS via uname).
- Very specific: line 49
If the user selected any integration surface (Linear, GitHub, Slack), check for agent-browser:
- Distinctive: line 67
Do NOT block on this — it's optional.
- Distinctive: line 71
Check if already installed:
- Distinctive: line 77
If not found, install using the user's preferred package manager:
- Very specific: line 105
If ~/.cyrus/.env already exists, note it and inform the user that existing values will be preserved.
≈ “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.
Setup Prerequisites
Checks system prerequisites and installs cyrus-ai.
Step 1: Detect Package Manager
If the user hasn't already specified their preferred package manager, ask:
Which package manager do you prefer? npm, pnpm, bun, or yarn?
Store the answer for use in this and subsequent skills.
Step 2: Check System Dependencies
Run the following checks and report results:
# Node.js >= 18
node --version
# jq (required for Claude Code parsing)
jq --version
# GitHub CLI (required for GitHub integration)
gh --versionFor each missing dependency, provide the install command:
| Dependency | macOS | Linux/Ubuntu |
| Node.js | brew install node | curl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - && sudo apt install -y nodejs |
| jq | brew install jq | sudo apt install -y jq |
| gh | brew install gh | See https://github.com/cli/cli/blob/trunk/docs/install_linux.md |
If all dependencies are present, print a checkmark for each and continue.
If any are missing, offer to install them (detect OS via uname). Wait for user confirmation before installing.
Step 3: Check for agent-browser (Optional)
If the user selected any integration surface (Linear, GitHub, Slack), check for agent-browser:
which agent-browserIf installed, ensure it's up to date:
npm update -g agent-browserIf not found, inform the user:
agent-browseris optional but enables automated app creation for Linear/GitHub/Slack. Without it, you'll be guided through manual setup steps instead.Install with:
npm install -g agent-browser
Do NOT block on this — it's optional. Note whether it's available for downstream skills.
Step 4: Install cyrus-ai
Check if already installed:
which cyrusIf not found, install using the user's preferred package manager:
# npm
npm install -g cyrus-ai
# pnpm
pnpm install -g cyrus-ai
# bun
bun install -g cyrus-ai
# yarn
yarn global add cyrus-aiVerify installation:
cyrus --versionStep 5: Ensure ~/.cyrus directory exists
mkdir -p ~/.cyrusIf ~/.cyrus/.env already exists, note it and inform the user that existing values will be preserved.
Completion
Print a summary:
Prerequisites:
✓ Node.js v22.x
✓ jq 1.7
✓ gh 2.x
✓ cyrus-ai installed
✓ agent-browser available (or: ⚠ not installed — manual setup mode)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.

