agentleFS
ceedaragentsceedaragents/cyrus/skills/cyrus-setup-prerequisites/SKILL.md

cyrus-setup-prerequisites

Skill888 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

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
  1. Distinctive:

    If the user hasn't already specified their preferred package manager, ask:

    line 14
  2. Distinctive:

    Run the following checks and report results:

    line 22
  3. Distinctive:

    If all dependencies are present, print a checkmark for each and continue.

    line 43
  4. Very specific:

    If any are missing, offer to install them (detect OS via uname).

    line 45
  5. Very specific:

    If the user selected any integration surface (Linear, GitHub, Slack), check for agent-browser:

    line 49
  6. Distinctive:

    Do NOT block on this — it's optional.

    line 67
  7. Distinctive:

    Check if already installed:

    line 71
  8. Distinctive:

    If not found, install using the user's preferred package manager:

    line 77
  9. Very specific:

    If ~/.cyrus/.env already exists, note it and inform the user that existing values will be preserved.

    line 105

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 --version

For each missing dependency, provide the install command:

DependencymacOSLinux/Ubuntu
Node.jsbrew install nodecurl -fsSL https://deb.nodesource.com/setup_22.x | sudo -E bash - && sudo apt install -y nodejs
jqbrew install jqsudo apt install -y jq
ghbrew install ghSee 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-browser

If installed, ensure it's up to date:

npm update -g agent-browser

If not found, inform the user:

agent-browser is 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 cyrus

If 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-ai

Verify installation:

cyrus --version

Step 5: Ensure ~/.cyrus directory exists

mkdir -p ~/.cyrus

If ~/.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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.