rudder-terraform — Claude Code plugin: what it does, install
This plugin guides Terraform workflows for RudderStack workspaces. Use it to configure the provider, manage resources, and run plan and apply cycles.
/plugin marketplace add anthropics/claude-plugins-community
/plugin install rudder-terraform@claude-communityWhat rudder-terraform does
rudder-terraform provides a Terraform workflow for RudderStack workspaces. It covers provider setup, resource and data-source usage, plus the init, plan, and apply cycle.
The plugin also addresses Terraform module structure and state management. Terraform provider setup is required before these workflows can be applied to a workspace.
What it helps with
- configure the RudderStack Terraform provider
- define workspace resources in Terraform
- read workspace data through data sources
- run the
init,plan, andapplycycle - organize Terraform modules and state
Example prompts for the agent
- Set up the Terraform provider for my RudderStack workspace.
- Show how to define a RudderStack resource and review the changes with
plan. - Organize this configuration into Terraform modules and explain the state workflow.
How to install rudder-terraform
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install rudder-terraform@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about rudder-terraform
How do I install rudder-terraform in Claude Code?
Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then install the plugin with /plugin install rudder-terraform@claude-community.
What does rudder-terraform do?
It guides Terraform management of RudderStack workspaces, including provider setup, resources, data sources, init, plan, and apply.
What does rudder-terraform require?
The RudderStack Terraform provider must be set up first. The workflow also covers module structure and state management.
Source text
rudder-terraform · MIT
🚀 Just launched <b><a href="https://www.rudderstack.com/product/rudderai/">RudderAI</a></b> - the agentic layer for the entire customer data lifecycle
# RudderStack Agent Skills
[](https://skills.sh/rudderlabs/rudder-agent-skills)
[](https://agentskills.io)
[](https://code.claude.com/docs/en/plugins)
[](https://cursor.directory/plugins/rudder-agent-skills)
[](https://mcp.rudderstack.com/docs)
[](https://github.com/rudderlabs/rudder-iac)
[](https://github.com/vercel-labs/skills#supported-agents)
[](LICENSE)
[](https://github.com/rudderlabs/rudder-agent-skills/stargazers)
A Claude Code plugin **marketplace** and [Agent Skills](https://agentskills.io) collection that teaches your AI coding agent how to drive every programmatic [RudderStack](https://www.rudderstack.com/) surface — CLI, MCP server, Terraform, Profiles, and AI events — 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 six plugins. Install the ones you use.
| Plugin | Status | Scope |
|---|---|---|
| [`rudder-core`](plugins/rudder-core/) | ✅ Available | Cross-tool domain knowledge: data catalog, tracking plans, data graphs, instrumentation planning & debugging |
| [`rudder-cli`](plugins/rudder-cli/) | ✅ Available | Workflows for [`rudder-cli`](https://github.com/rudderlabs/rudder-iac) and [`rudder-typer`](https://www.rudderstack.com/docs/features/ruddertyper/) |
| [`rudder-mcp`](plugins/rudder-mcp/) | ✅ Available | Workflows for [RudderStack's hosted MCP server](https://mcp.rudderstack.com/docs) at `mcp.rudderstack.com` |
| [`rudder-terraform`](plugins/rudder-terraform/) | ✅ Available | Workflows for the [Terraform provider](https://github.com/rudderlabs/terraform-provider-rudderstack) |
| [`rudder-profiles`](plugins/rudder-profiles/) | ✅ Available | Workflows for [RudderStack Profiles](https://github.com/rudderlabs/profiles-mcp): setup, project creation, analysis, updates, and debugging |
| [`rudder-ai-events`](plugins/rudder-ai-events/) | ✅ Available | Onboard an existing app to RudderStack AI events with [`@rudderstack/ai`](https://www.npmjs.com/package/@rudderstack/ai) (Node.js), [`rudderstack-ai`](https://pypi.org/project/rudderstack-ai/) (Python) and `ai-sdk-go` (Go): discover, plan, instrument, verify |
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](https://github.com/vercel-labs/skills) installs these skills into Claude Code, Cursor, Cline, OpenCode, and [40+ agents](https://github.com/vercel-labs/skills#supported-agents):
```bash
# 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
```bash
/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](https://cursor.directory/plugins/rudder-agent-skills) with **Add to Cursor**, or use the Skills CLI:
```bash
npx skills add rudderlabs/rudder-agent-skills -a cursor
```
> Manual symlink, git submodule, agent-specific paths, and troubleshooting live in [`docs/installation.md`](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 |
### `rudder-ai-events`
| Skill | When to use |
|---|---|
| `rudder-ai-events-setup` | Onboarding an app to AI events: discovering chat, background-agent, browser and MCP server surfaces and planning `ai-events.yaml` |
| `rudder-ai-events-instrument` | Adding the AI events code from an approved `ai-events.yaml`, including MCP server wrappers |
| `rudder-ai-events-verify` | Validating captured AI events against the spec before real traffic |
## How skills work together
```mermaid
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, rudder-ai-events
├── .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](https://github.com/vercel-labs/skills)).
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 |
| `rudder-ai-events` | `/rudder-ai-events-setup` | Plans AI events for your app in `ai-events.yaml`; `/rudder-ai-events-instrument` then adds the pinned SDK |
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](CONTRIBUTING.md) for authoring conventions, testing steps, and PR expectations.
## License
MIT License — see [LICENSE](LICENSE) for details.
© rudderlabs · MIT · rudderlabs/rudder-agent-skills