rudder-cli-workflowlisted
Install: claude install-skill rudderlabs/rudder-agent-skills
# Rudder CLI Development Workflow
## Overview
Iterative development workflow for RudderStack resources using `rudder-cli`. Follow the validate → dry-run → apply cycle to ensure correctness before making changes to workspaces.
## Prerequisites: Authentication
Before running any commands that interact with a workspace, verify authentication:
```bash
# Check if authenticated and show current workspace
rudder-cli workspace info --json
```
**If authenticated**, you'll see workspace details. `workspaceID` and `name` identify the workspace:
```json
{
"dataPlaneURL": "https://example.dataplane.rudderstack.com",
"environment": "PRODUCTION",
"name": "My Workspace",
"region": "US",
"status": "ACTIVE",
"workspaceID": "2iKXWU4QnqclkpPIfXfsbBqrAVa"
}
```
**If NOT authenticated**, the command exits non-zero with an error. rudder-cli reads the token from the `RUDDERSTACK_ACCESS_TOKEN` environment variable, or from the config file that `rudder-cli auth login` writes. When the variable is set, it wins over the config file.
- **Agents:** use `RUDDERSTACK_ACCESS_TOKEN`. Do not run `rudder-cli auth login`, which prompts for the token on a terminal, and never ask the user to paste a token into the chat. Ask the user to export the variable in the shell that starts the agent, restart the agent, and re-run `rudder-cli workspace info --json`. `rudder-cli-setup` has the exact command.
- **People at a terminal:** `rudder-cli auth login` prompts for the token and saves it.
Get a toke