Rpk Redpanda
Operate a self-managed Redpanda broker node from the CLI with the `rpk redpanda` command group and `rpk iotune`, and look up node commands and broker properties in the Redpanda docs. Use when starting, stopping, or restarting a broker, preparing a node for production, switching between production, development, and recovery mode, running the autotuner or benchmarking disks with iotune, bootstrapping or editing redpanda.yaml, or taking a broker down for a reboot or upgrade. Self-managed only: these commands act on the broker host and don't apply to Redpanda Cloud. For cluster-wide operations (cl
Install
/plugin marketplace add redpanda-data/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add redpanda-data/skills --skill rpk-redpandagit clone --depth 1 https://github.com/redpanda-data/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/rpk-redpanda ~/.claude/skills/rpk-redpandaPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# rpk redpanda `rpk redpanda` operates one Redpanda broker on its own host: it starts and stops the process, sets the node's mode, tunes the kernel, and edits the local `redpanda.yaml`. This skill keeps only the product-specific procedure below. Look up everything else in the docs (last section). ## How to work **Check developer mode before you start a broker that holds real data.** Read the node's `redpanda.yaml` first. When `redpanda.developer_mode` is `true` and no `--mode` is given, `rpk redpanda start` runs in `dev-container` mode, which bypasses fsync and can lose data, and `rpk redpanda start --mode dev-container` saves `developer_mode: true` for every later start. On a production broker, run `rpk redpanda mode production` (or ask the user) before you start it. Never use `--mode dev-container` on a node that serves real data. **Drain a broker before you stop it.** When a broker is part of a running cluster, run `rpk cluster maintenance enable <broker-id> --wait` first so its partition leadership moves to other brokers, then stop Redpanda on it. Turn maintenance mode off with `rpk cluster maintenance disable <broker-id>` once it is back. **Don't run the autotuner on Azure.** In Azure self-managed environments, don't apply the tuners: no `rpk redpanda tune`, no `rpk redpanda start --tune`, and no `redpanda-tuner` service. Other production preparation, such as production mode, `rpk iotune`, and `rpk redpanda check`, still applies.
Details
- Skill name
rpk-redpanda- Repository
- redpanda-data/skills
- Path
skills/rpk-redpanda/SKILL.md- License
- Apache-2.0
- Repo updated
- 16 November 2026
FAQ
What does the Rpk Redpanda skill do?
Operate a self-managed Redpanda broker node from the CLI with the `rpk redpanda` command group and `rpk iotune`, and look up node commands and broker properties in the Redpanda docs. Use when starting, stopping, or restarting a broker, preparing a node for production, switching between production, development, and recovery mode, running the autotuner or benchmarking disks with iotune, bootstrapping or editing redpanda.yaml, or taking a broker down for a reboot or upgrade. Self-managed only: these commands act on the broker host and don't apply to Redpanda Cloud. For cluster-wide operations (cl
How do I install the Rpk Redpanda skill?
Claude Code plugin: /plugin marketplace add redpanda-data/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Rpk Redpanda popular?
It lives in redpanda-data/skills, which has 9 GitHub stars and 4 forks.
Related skills
Adp
9redpanda-data/skills
Redpanda's Agentic Data Plane: governance infrastructure for building, running, and governing AI agents and MCP servers behind a credential-injecting AI Gateway for LLM providers, operated through the `rpk ai` CLI and the ADP UI at ai.redpanda.com. Use when installing `rpk ai`, signing in to an environment, checking setup with `rpk ai doctor`, managing managed or self-managed AI agents and their triggers with `rpk ai agent` and `rpk ai trigger`, configuring remote or managed MCP servers with `rpk ai mcp-server` (including code mode and user-delegated OAuth), setting up LLM providers and models
Adp Governance
9redpanda-data/skills
Govern what Agentic Data Plane agents may do, spend, and expose, through the `rpk ai` CLI and the ADP UI at ai.redpanda.com, and look up governance features in the Redpanda docs. Use when writing or debugging a Cedar access policy with `rpk ai policy`, giving a new agent access, capping agent spend with `rpk ai budget`, analyzing cost, attaching a guardrail to a provider, containing or releasing an agent with the kill switch, storing or deleting a credential with `rpk ai secret`, minting an API key, masking MCP tool data with data policies, or setting up inbound or outbound OAuth. For signing
Adp Observability
9redpanda-data/skills
Read what Agentic Data Plane agents did and why, through traces, conversation transcripts, the audit log, and the monitoring views in the ADP UI at ai.redpanda.com and the `rpk ai` CLI. Use when finding which call made an agent run slow, failed, or expensive with `rpk ai trace`, reading or filtering a conversation with `rpk ai agent transcript`, finding conversations with a failed tool call, investigating a denied or masked call with `rpk ai auditlog`, working out on whose behalf an agent acted, or reading the Agent network or Home views. For budgets, cost, and access policies, see `/redpanda:
Streaming
9redpanda-data/skills
Works with the Redpanda broker through its Kafka-compatible API, and looks up broker, topic, and client behavior in the Redpanda docs. Use when producing to or consuming from Redpanda, choosing or configuring a Kafka client, working with consumer groups, offsets, idempotent producers, or transactions, creating or configuring topics, or using Tiered Storage, Iceberg Topics, Cloud Topics, Continuous Data Balancing, Shadow Linking, Leader Pinning, or Schema ID Validation. For the Admin HTTP API, see /redpanda:streaming-admin-api; for diagnosing a cluster, see /redpanda:streaming-debugging; for rp
Rpk Debug
9redpanda-data/skills
Collect Redpanda diagnostics bundles with the `rpk debug` command group, and look up bundle flags, contents, and procedures in the Redpanda docs. Use when collecting a debug bundle for Redpanda Support or self-triage, running `rpk debug bundle` on a broker host or inside a Kubernetes pod, collecting a cluster-wide bundle through the Admin API with `rpk debug remote-bundle`, or reading a bundle to triage a problem such as an Enterprise feature that stopped working. Applies to self-managed deployments only. For client-side triage of a Redpanda Cloud cluster, see /redpanda:rpk-cluster and /redpan
Streaming Admin API
9redpanda-data/skills
Operate a self-managed Redpanda cluster through its HTTP Admin API (port 9644) and its ConnectRPC services, and look up endpoints, request bodies and auth levels in the Redpanda docs. Use when calling the Admin API directly with curl or a script instead of rpk: brokers and decommissioning, maintenance mode and restarts, partitions and replica moves, cluster config, health, licensing and enterprise features, security users and RBAC roles, debug endpoints and debug bundles, and Shadow Linking (ShadowLinkService create, update, failover) for disaster recovery. For the same tasks with rpk, see /re
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.