Skip to content
Development
Skill

/rudder-cli-setup

Installs and authenticates rudder-cli. Use when installing rudder-cli, setting up rudder cli, rudder-cli command not found, or authenticating with RudderStack

From plugin
rudder-agent-skills
1823 skills
Install
$ npx -y skills add rudderlabs/rudder-agent-skills --skill rudder-cli-setup --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/rudder-cli-setup

Context preview

The summary Claude sees to decide when to auto-load this skill.

Installs and authenticates rudder-cli. Use when installing rudder-cli, setting up rudder cli, rudder-cli command not found, or authenticating with RudderStack

SKILL.md

rudder-cli-setup.SKILL.md
name: rudder-cli-setup
description: Installs and authenticates rudder-cli. Use when installing rudder-cli, setting up rudder cli, rudder-cli command not found, or authenticating with RudderStack
allowed-tools: "Bash(which, curl, chmod, uname, rudder-cli *), Read, Write, Edit"

Rudder CLI Setup

Install rudder-cli, authenticate with RudderStack, and verify the setup works.

Setup Workflow

1. Check Installation ──► which rudder-cli
         │
         ├── Found ──► Skip to Authentication
         │
         └── Not Found ──► Install from GitHub Releases
                                    │
2. Verify Installation ◄────────────┘
         │
         └── rudder-cli --version

3. Check Authentication ──► rudder-cli workspace info
         │
         ├── Authenticated ──► Done! Show workspace info
         │
         └── Not Authenticated ──► Guide through auth flow

Step 1: Check if Installed

which rudder-cli

**If found:** Skip to Step 3 (Authentication).

**If not found:** Continue to Step 2 (Installation).

Step 2: Install rudder-cli

Detect Operating System

uname -s
  • `Darwin` = macOS
  • `Linux` = Linux

Download from GitHub Releases

Go to: https://github.com/rudderlabs/rudder-iac/releases

Download the appropriate binary for your OS and architecture:

| OS | Architecture | Binary Name | |----|--------------|-------------| | macOS | Intel | `rudder-cli_darwin_amd64` | | macOS | Apple Silicon | `rudder-cli_darwin_arm64` | | Linux | x86_64 | `rudder-cli_linux_amd64` | | Linux | ARM64 | `rudder-cli_linux_arm64` | | Windows | x86_64 | `rudder-cli_windows_amd64.exe` |

Installation Commands (macOS/Linux)

# Example for macOS Apple Silicon - adjust URL for your platform
# Check latest version at https://github.com/rudderlabs/rudder-iac/releases

# Download (replace VERSION and BINARY with actual values)
curl -L -o rudder-cli https://github.com/rudderlabs/rudder-iac/releases/download/VERSION/BINARY

# Make executable
chmod +x rudder-cli

# Move to PATH (choose one)
sudo mv rudder-cli /usr/local/bin/    # System-wide
# OR
mv rudder-cli ~/.local/bin/           # User-only (ensure ~/.local/bin is in PATH)

Verify Installation

rudder-cli --version

Expected output: Version number (e.g., `rudder-cli version 0.x.x`)

Step 3: Authenticate

Check Current Status

rudder-cli workspace info

**If authenticated:** Shows workspace name and ID. You're done!

**If not authenticated:** Continue with authentication.

Get Access Token

1. Log in to your RudderStack dashboard 2. Go to **Settings → Access Tokens** 3. Click **Generate New Token** 4. Copy the token (you won't see it again)

Run Authentication

rudder-cli auth login

This prompts for your access token. Paste it when asked.

Verify Authentication

rudder-cli workspace info

Expected output:

Workspace Information:
  ID:   2iKXWU4QnqclkpPIfXfsbBqrAVa
  Name: My Workspace

Credential Security

  • **Never echo or log your access token**
  • Store tokens in environment variables if needed: `RUDDER_ACCESS_TOKEN`
  • Add `.env` files to `.gitignore`
  • For CI/CD, use repository secrets
  • Rotate tokens periodically in the RudderStack dashboard

Troubleshooting

| Issue | Solution | |-------|----------| | `command not found` after install | Check PATH includes install location | | `unauthorized` error | Re-run `rudder-cli auth login` with new token | | Wrong workspace | Token is tied to workspace; generate new token in correct workspace | | Download fails | Check network; try browser download from releases page |

Next Steps

After setup completes:

  • Run `/rudder-environment-check` to verify full environment
  • Start with `/rudder-cli-workflow` for validate → dry-run → apply cycles
Read more
Ships withrudder-agent-skills

A Claude Code plugin marketplace and Agent Skills collection that teaches your AI coding agent how to drive every programmatic RudderStack surface — CLI, MCP server, Terraform, and Profiles — with the right preflight checks, commands, and recovery paths.

Get the whole plugin

Other skills on rudder-agent-skills.