Redpanda Agent Skills

Agent Skills for Redpanda's products — Streaming (the Kafka-compatible engine), SQL (Oxla), Connect, and Cloud (Serverless, BYOC, Dedicated) — unified by the rpk command-line experience. Each skill is grounded in Redpanda's own source code, documentation, and APIs.

Installation

One command (from your shell):

claude plugin marketplace add redpanda-data/skills && claude plugin install redpanda@redpanda-skills

Or inside a Claude Code session, as two separate slash commands (run one at a time — don't paste them together):

/plugin marketplace add redpanda-data/skills
/plugin install redpanda@redpanda-skills

Once installed, invoke any skill with its /redpanda:<skill> name (e.g. /redpanda:streaming). Each skill's SKILL.md frontmatter description tells the agent when to load it automatically.

What is this?

This repo is a Claude Code plugin named redpanda. When installed, every skill is available to the agent as /redpanda:<skill> (for example /redpanda:streaming). A skill is a focused, on-demand reference: a SKILL.md the agent loads when relevant, plus references/ files it pulls in for depth. Skills are self-contained and contain copy-pasteable commands, configs, and code.

Available Skills

Redpanda has four public products — Streaming, SQL, Connect, and Cloud — with rpk as the unifying CLI across all of them.

🌊 Streaming

The Kafka-compatible streaming engine (the Redpanda broker).

• streaming — The Kafka API: produce/consume, consumer groups, transactions & idempotence, topic management, client compatibility, tiered storage, Iceberg topics, cloud topics, continuous balancing, and shadow linking.
• streaming-admin-api — Operate the cluster via the HTTP Admin API (port 9644): brokers, partitions, cluster config, features, licensing, transactions, debug, and debug bundles.
• streaming-debugging — Diagnose a broker/cluster: debug bundles, metrics endpoints, logs, CPU profiling, partition/raft health, and failure-mode playbooks.

🧮 SQL

Redpanda SQL — the distributed, columnar, PostgreSQL-compatible analytical database (Oxla).

• sql — Write SQL: connection (PostgreSQL wire protocol), data types, DDL/DML, functions, and analytical queries.
• sql-admin-api — Operate a cluster: configuration, node roles and ports, leader election, storage backends, memory limits, and the gRPC admin service.
• sql-federated-queries — Query external data: Kafka topics via catalogs, Apache Iceberg tables, and S3/GCS/Azure parquet/ORC files.
• sql-debugging — Diagnose: system catalog tables, Prometheus metrics, log levels, memory/OOM monitoring, and query troubleshooting.

🔌 Connect

Redpanda Connect — declarative stream processing (formerly Benthos).

• connect — Build pipelines (inputs, processors, outputs, Bloblang), the config structure, and running pipelines.
• connect-debugging — Debug pipelines: linting, log levels, metrics, tracing, health endpoints, dry-runs, and common failure modes.

Change Data Capture (one per connector):

• connect-cdc-postgres — PostgreSQL (postgres_cdc, logical replication / WAL).
• connect-cdc-mysql — MySQL/MariaDB (mysql_cdc, binlog).
• connect-cdc-mongodb — MongoDB (mongodb_cdc, change streams).
• connect-cdc-sqlserver — Microsoft SQL Server (microsoft_sql_server_cdc).
• connect-cdc-oracle — Oracle (oracledb_cdc, LogMiner).
• connect-cdc-spanner — Google Cloud Spanner (gcp_spanner_cdc, change streams).
• connect-cdc-dynamodb — AWS DynamoDB (aws_dynamodb_cdc, DynamoDB Streams).
• connect-cdc-salesforce — Salesforce (salesforce_cdc, Pub/Sub API).

☁️ Cloud

Redpanda Cloud — the managed control plane and per-cluster data plane.

• cloud-serverless — Serverless clusters (multi-tenant, pay-per-use) via the Control Plane API, plus the per-cluster Data Plane API.
• cloud-byoc — BYOC (Bring Your Own Cloud) clusters in your own AWS/GCP/Azure account: networks/VPCs, provider setup, and the rpk BYOC agent flow.
• cloud-dedicated — Dedicated clusters (fully Redpanda-managed, single-tenant, in Redpanda's cloud account) via the Control Plane API.

⌨️ rpk — the unifying CLI

One CLI across every product.

• rpk — Install rpk, configure connections with profiles and -X flags, and target self-hosted or Redpanda Cloud clusters. Start here.
• rpk-topic — Create, describe, alter, and delete topics; produce and consume records.
• rpk-cluster — Health/metadata, brokers, cluster config, partition balancing/movement, maintenance mode, quotas, storage (mountable topics / whole-cluster restore), and self-tests.
• rpk-group — List/describe consumer groups, inspect lag and members, reset/seek offsets, and delete groups or offsets.
• rpk-security — Manage SASL/SCRAM users, Kafka ACLs, RBAC roles, and secrets.
• rpk-cloud — Authenticate to Redpanda Cloud, manage credentials, select clusters, manage resource groups, and drive BYOC provisioning.
• rpk-debug — Collect local and remote debug bundles and inspect local process info.
• rpk-registry — Manage Schema Registry subjects, schemas, compatibility, and modes.
• rpk-transform — Build, deploy, and manage Redpanda Data Transforms (in-broker WebAssembly functions).
• ai — The rpk ai / MCP subcommands: expose Redpanda operations to AI agents over the Model Context Protocol.

How these skills were built

Each skill was drafted from a grounded spec (source paths into the Redpanda, Connect, and Oxla repositories plus the docs), then put through an adversarial review at maximum model effort that cross-checks every command, flag, config field, endpoint, and code example against the actual source — fixing hallucinated or outdated details — followed by a dedicated enterprise-feature coverage pass (the key differentiators, with their nested settings) and a final verification pass.

License

Distributed under the Apache 2.0 license. See the LICENSE file.

Acknowledgements

Structure and format modeled on google/skills.