Skip to main content
skill CX Codex

cyrus-setup-prerequisites — Claude Code skill: check Cyrus

Checks Node.js, jq and gh CLI, installs the cyrus-ai package and creates ~/.cyrus before you configure Cyrus.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add cyrusagents/cyrus --skill cyrus-setup-prerequisites -a claude-code
Open on GitHub

What cyrus-setup-prerequisites does

The skill walks your system and reports what is already there: Node.js 18 or newer, jq for parsing Claude output, GitHub CLI for GitHub integration. Anything missing comes with an install command for macOS or Linux, and it waits for your confirmation before running it. It asks which package manager you prefer — npm, pnpm, bun or yarn — and stores the answer for later skills.

Then it installs cyrus-ai with that manager and creates ~/.cyrus. If ~/.cyrus/.env already exists, the skill notes it and keeps the current values. One rule is baked in: never touch .env or any file under ~/.cyrus/ with Read, Edit or Write — only Bash with grep and printf >>, so secrets stay out of the conversation context. Worth remembering if you plan to fork the skill.

agent-browser gets its own check, and only when you picked Linear, GitHub or Slack as an integration surface. Without it you go through manual setup steps, but nothing blocks. At the end you get a summary: what was found, what was installed, what is still missing.

What it helps with

  • check Node.js, jq and gh versions before installing Cyrus
  • install cyrus-ai through npm, pnpm, bun or yarn
  • create ~/.cyrus without overwriting an existing .env
  • find out whether agent-browser is available for automated integration setup
  • get install commands for missing dependencies on macOS and Linux

Example prompts for the agent

  • check the Cyrus prerequisites and install cyrus-ai
  • which package manager should I use for Cyrus?
  • is agent-browser installed on this machine?

How to install cyrus-setup-prerequisites

1Skills CLI (Vercel)

npx skills add cyrusagents/cyrus --skill cyrus-setup-prerequisites -a claude-code

2Manually: put the files in place

~/.claude/skills/cyrus-setup-prerequisites/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cyrus-setup-prerequisites/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cyrus-setup-prerequisites

How do I install cyrus-setup-prerequisites in Claude?

Run npx skills add cyrusagents/cyrus --skill cyrus-setup-prerequisites -a claude-code. The skill lands in ~/.claude/skills/cyrus-setup-prerequisites/SKILL.md.

What does cyrus-setup-prerequisites do?

It checks Node.js, jq and gh CLI, offers install commands for anything missing, installs the cyrus-ai package and creates the ~/.cyrus directory.

What do I need before running it?

Node.js 18 or newer, jq and GitHub CLI. The skill asks which package manager you prefer, and agent-browser matters only for automated Linear, GitHub and Slack setup.

Source text

SKILL.md · Apache-2.0
---
name: cyrus-setup-prerequisites
description: Check and install prerequisites for Cyrus — Node.js, jq, gh CLI, and the cyrus-ai npm package.
---

**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:

```bash
# 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:

| 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`:

```bash
which agent-browser
```

**If installed**, ensure it's up to date:

```bash
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:

```bash
which cyrus
```

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

```bash
# 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:

```bash
cyrus --version
```

## Step 5: Ensure ~/.cyrus directory exists

```bash
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)
```

© cyrusagents · Apache-2.0 · cyrusagents/cyrus

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set19

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor