RudderStack Agent Skills
Learn about RudderStack Agent Skills and how they teach AI coding agents to drive the Rudder CLI, MCP server, Terraform, and Profiles.
This page introduces RudderStack Agent Skills, a marketplace of skills that teach your AI coding agent how to drive the Rudder CLI, MCP server, Terraform, and Profiles.
Overview
RudderStack Agent Skills is an open Agent Skills marketplace that teaches your AI coding agent how to drive the following programmatic RudderStack surfaces with the right preflight checks, commands, and recovery paths:
A skill is a folder containing a SKILL.md file with instructions that your agent loads on demand. Instead of guessing at commands, your agent follows the workflows RudderStack recommends — validating specs before applying them, previewing changes with a dry run, and recovering from common errors.
The marketplace is open source at github.com/rudderlabs/rudder-agent-skills and listed on skills.sh and cursor.directory.
Marketplace plugins
The marketplace bundles five plugins. Install rudder-core for cross-tool domain knowledge, plus whichever tool plugins you use.
| Plugin | Coverage |
|---|
rudder-core | Cross-tool domain knowledge: Data Catalog, Tracking Plans, data graphs, instrumentation planning, and debugging |
rudder-cli | Workflows for the Rudder CLI and RudderTyper: validate, dry-run, apply, import, and transformations |
rudder-mcp | Workflows for connecting AI agents to the RudderStack MCP server at mcp.rudderstack.com |
rudder-terraform | Workflows for the RudderStack Terraform provider: setup, resources, and plan/apply cycles |
rudder-profiles | Workflows for RudderStack Profiles: setup, project creation, analysis, updates, and debugging |

Domain knowledge lives in rudder-core, so it never duplicates across the tool-specific plugins.
Available skills
The following skills are available in the marketplace:
rudder-core
| Skill | When it helps |
|---|
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 an event taxonomy from scratch or restructuring one |
rudder-instrumentation-debugging | Fixing validation errors, schema issues, or instrumentation problems |
rudder-destination-debugging | Diagnosing why events fail, drop, or don’t arrive at a destination |
rudder-environment-check | Checking prerequisites and setup status |
rudder-cli
| Skill | When it helps |
|---|
rudder-cli-workflow | Iterating on resources with validate, dry-run, and apply |
rudder-import-and-evolve | Importing existing RudderStack resources to CLI management |
rudder-typer-workflow | Generating type-safe SDKs from Tracking Plans |
rudder-transformations | Creating, editing, or managing transformations and libraries |
rudder-cli-setup | Installing and authenticating the Rudder CLI |
rudder-mcp
| Skill | When it helps |
|---|
rudder-mcp-workflow | Connecting AI agents to RudderStack via the MCP server |
rudder-mcp-setup | Configuring your agent to connect to the MCP server |
| Skill | When it helps |
|---|
rudder-terraform-workflow | Managing RudderStack resources via the Terraform provider |
rudder-terraform-setup | Installing Terraform and the RudderStack provider |
rudder-profiles
| Skill | When it helps |
|---|
rudder-profiles-setup | Installing and wiring the Profiles toolchain and Profiles MCP |
rudder-profiles-project | Bootstrapping a new Profiles project from warehouse resources |
rudder-profiles-understand | Explaining an existing Profiles project and its outputs |
rudder-profiles-update | Updating a project with features, inputs, propensity, or incremental changes |
rudder-profiles-debug | Diagnosing compile failures, run failures, and output-quality issues |
Get started
Questions? We're here to help.
Join the RudderStack Slack community or email us for support