🚀 Just launched RudderAI - the agentic layer for the entire customer data lifecycle
RudderStack 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. Works with Claude Code, Cursor, and 40+ agents.
What's inside
One marketplace (rudder-agent-skills) bundling five plugins. Install the ones you use.
Most users drive RudderStack with more than one tool. Install rudder-core plus whichever tool plugins you use; the domain knowledge lives in rudder-core so it never duplicates across tool-specific plugins.
Installation
One command, any agent — no cloning, no local setup.
Any agent — Skills CLI (recommended)
The Skills CLI installs these skills into Claude Code, Cursor, Cline, OpenCode, and 40+ agents:
# Interactive — pick skills and your agent
npx skills add rudderlabs/rudder-agent-skills
# Or: list first · install everything globally · target one agent
npx skills add rudderlabs/rudder-agent-skills --list
npx skills add rudderlabs/rudder-agent-skills -g --all
npx skills add rudderlabs/rudder-agent-skills -a claude-code --skill rudder-cli-workflow
# Update anytime
npx skills update
Claude Code — plugin marketplace
/plugin marketplace add rudderlabs/rudder-agent-skills
/plugin install rudder-core@rudder-agent-skills # then add whichever tool plugins you use
Non-interactive equivalent: claude plugin marketplace add rudderlabs/rudder-agent-skills then claude plugin install <plugin>@rudder-agent-skills. Update with /plugin marketplace update rudder-agent-skills.
Cursor
Add it straight from the cursor.directory listing with Add to Cursor, or use the Skills CLI:
npx skills add rudderlabs/rudder-agent-skills -a cursor
Manual symlink, git submodule, agent-specific paths, and troubleshooting live in docs/installation.md.
Available skills
rudder-core
| Skill | When to use |
|---|
rudder-data-catalog | Creating or managing events, properties, categories, or custom types |
rudder-data-graphs | Modeling entities, events, and relationships for Audiences |
rudder-tracking-plans | Creating tracking plans to group events for specific sources |
rudder-instrumentation-planning | Designing event taxonomy from scratch or restructuring |
rudder-instrumentation-debugging | Fixing validation errors, schema issues, or instrumentation problems |
rudder-environment-check | Checking prerequisites and setup status |
rudder-cli
| Skill | When to use |
|---|
rudder-cli-workflow | Iterating on RudderStack resources with validate → dry-run → apply |
rudder-import-and-evolve | Importing existing RudderStack resources to CLI management |
rudder-typer-workflow | Generating type-safe SDKs (Swift/Kotlin) from tracking plans |
rudder-transformations | Creating, editing, or managing transformations and libraries |
rudder-cli-setup | Installing and authenticating rudder-cli |
rudder-mcp
| Skill | When to use |
|---|
rudder-mcp-workflow | Connecting AI/LLM agents to RudderStack via MCP server |
rudder-mcp-setup | Configuring Claude Code to connect to MCP server |
rudder-terraform
| Skill | When to use |
|---|
rudder-terraform-workflow | Managing RudderStack resources via Terraform provider |
rudder-terraform-setup | Installing Terraform and the RudderStack provider |
rudder-profiles
| Skill | When to use |
|---|
rudder-profiles-setup | Installing and wiring the Profiles toolchain and Profiles MCP |
rudder-profiles-project | Bootstrapping a new Profiles project from discovered warehouse resources |
rudder-profiles-understand | Explaining an existing Profiles project, its features, and latest outputs |
rudder-profiles-update | Updating a Profiles project with features, inputs, propensity, or incremental changes |
rudder-profiles-debug | Diagnosing compile failures, run failures, and output-quality issues |
How skills work together
flowchart TD
plan["rudder-instrumentation-planning<br/>design the taxonomy"]
plan --> catalog["rudder-data-catalog<br/>build the vocabulary"]
plan --> evolve["rudder-import-and-evolve<br/>adopt existing resources"]
plan --> plans["rudder-tracking-plans<br/>group events per source"]
catalog --> cli["rudder-cli-workflow<br/>validate → dry-run → apply"]
evolve --> cli
plans --> cli
cli --> typer["rudder-typer-workflow<br/>generate typed SDKs"]
cli --> transform["rudder-transformations<br/>transform events"]
cli --> debug["rudder-instrumentation-debugging<br/>fix validation issues"]
Directory structure
rudder-agent-skills/
├── README.md # this file
├── CONTRIBUTING.md # authoring + PR guidelines
├── LICENSE
├── .claude-plugin/
│ └── marketplace.json # the marketplace catalog
├── docs/
│ └── installation.md # full install guide
├── examples/ # end-to-end worked examples
└── plugins/
└── <plugin>/ # rudder-core, rudder-cli, rudder-mcp, rudder-terraform, rudder-profiles
├── .claude-plugin/plugin.json
└── skills/
└── <skill>/
└── SKILL.md
Prerequisites
A compatible AI coding agent (Claude Code, Cursor, Cline, OpenCode, or any of the 40+ supported agents).
Each plugin includes a setup skill that guides you through installing and configuring tool-specific prerequisites:
| Plugin | Setup Skill | What it installs |
|---|
rudder-cli | /rudder-cli-setup | Downloads rudder-cli binary, authenticates with RudderStack |
rudder-mcp | /rudder-mcp-setup | Configures Claude Code to connect to RudderStack's MCP server at mcp.rudderstack.com |
rudder-terraform | /rudder-terraform-setup | Installs Terraform, configures the RudderStack provider |
rudder-profiles | /rudder-profiles-setup | Installs pb, configures profiles-mcp, and wires editor MCP settings |
After installing a plugin, run its setup skill to get started. Use /rudder-environment-check to verify your full setup.
Examples
examples/ contains worked end-to-end projects that demonstrate skills in action — the current example covers the transformations workflow.
Contributing
See CONTRIBUTING.md for authoring conventions, testing steps, and PR expectations.
License
MIT License — see LICENSE for details.
