How do I install the Danube Admin skill?

Run npx skillmds@latest add danube-messaging/danube-admin in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Danube Admin skill do?

Control plane operations with danube-admin. Use for cluster management, broker operations, topic/namespace management, schema administration, and security. It is listed under Security on SkillMD.

Is Danube Admin safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Danube Admin?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Danube Admin free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Danube Admin?

danube-messaging (@danube-messaging) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Danube Admin by danube-messaging — Agent Skill

Name: Danube Admin
Rating: 4.2 (5 reviews)
Author: danube-messaging

Skill: danube-admin — Control Plane Operations

Objective

Complete reference for danube-admin — the CLI tool for managing Danube clusters, brokers, topics, namespaces, schemas, and security. This operates on the control plane (admin gRPC port 50051).

Connection

# Set endpoint globally
export DANUBE_BROKER_ENDPOINT=http://localhost:50051

# Or per command
danube-admin --broker-endpoint http://broker1:50051 brokers list

Cluster (Raft Consensus)

Status

danube-admin cluster status

Raft Cluster Status:
  Self Node ID:  9823746501928374
  Raft Address:  127.0.0.1:7650
  Leader:        9823746501928374
  Term:          3
  Last Applied:  142
  Voters:        [9823746501928374, 1048209374659182, 7391028374651029]
  Learners:      [5829103746519283]

Field	Description
Self Node ID	The node you connected to
Leader	Current leader (`none` if no leader elected)
Term	Raft election counter
Last Applied	Last log entry applied
Voters	Nodes that participate in consensus
Learners	Nodes replicating but not voting

Add Node (Learner)

danube-admin cluster add-node --node-addr http://new-broker:50054

Promote Node (Learner → Voter)

danube-admin cluster promote-node --node-id <NODE_ID>

Remove Node

danube-admin cluster remove-node --node-id <NODE_ID>

Scale-Up Workflow

# 1. Check current cluster
danube-admin cluster status

# 2. Add as learner
danube-admin cluster add-node --node-addr http://new-broker:50054

# 3. Verify learner added
danube-admin cluster status

# 4. Promote to voter
danube-admin cluster promote-node --node-id <NODE_ID>

# 5. Activate for traffic
danube-admin brokers activate <BROKER_ID>

# 6. Verify balance
danube-admin brokers balance

Scale-Down Workflow

# 1. Drain topics
danube-admin brokers unload <BROKER_ID>

# 2. Remove from cluster
danube-admin cluster remove-node --node-id <NODE_ID>

# 3. Verify
danube-admin cluster status

Brokers

List Brokers

danube-admin brokers list

BROKER ID       STATUS   ADDRESS             ROLE             ADMIN ADDR          METRICS ADDR
----------------------------------------------------------------------------------------------
broker-001      active   127.0.0.1:6650      Cluster_Leader   127.0.0.1:50051     127.0.0.1:9040
broker-002      active   127.0.0.1:6651      Cluster_Follower 127.0.0.1:50052     127.0.0.1:9041
broker-003      active   127.0.0.1:6652      Cluster_Follower 127.0.0.1:50053     127.0.0.1:9042

Get Leader

danube-admin brokers leader

List Namespaces

danube-admin brokers namespaces

Cluster Balance

danube-admin brokers balance

Status:                    ✅ Well Balanced
Coefficient of Variation:  15.23%
Broker Details:
Broker ID       Load       Topics     Status
--------------------------------------------------
broker-001      5.00       5          OK
broker-002      4.00       4          OK

CV	Status
< 20%	Well Balanced
20–30%	Balanced
30–40%	Imbalanced — consider rebalancing
> 40%	Severely Imbalanced — rebalance recommended

Rebalance

# Preview moves first (always do this)
danube-admin brokers rebalance --dry-run

# Execute
danube-admin brokers rebalance

# Limit scope
danube-admin brokers rebalance --max-moves 10

Unload Broker (Drain Topics)

danube-admin brokers unload <BROKER_ID>

# Preview
danube-admin brokers unload <BROKER_ID> --dry-run

# With filters
danube-admin brokers unload <BROKER_ID> \
  --max-parallel 5 \
  --namespace-include default \
  --timeout 30

Activate Broker

danube-admin brokers activate <BROKER_ID> --reason "Maintenance completed"

Namespaces

List Topics in Namespace

danube-admin namespaces topics <NAMESPACE>

View Policies

danube-admin namespaces policies <NAMESPACE>

Create Namespace

danube-admin namespaces create production

Delete Namespace

danube-admin namespaces delete old-namespace

Warning: Deleting a namespace removes all topics within it. This is immediate and irreversible.

Topics

List Topics

danube-admin topics list --namespace default
danube-admin topics list --broker broker-001

Create Topic

# Simple topic (non-reliable delivery)
danube-admin topics create /default/logs

# With reliable delivery
danube-admin topics create /default/events --dispatch-strategy reliable

# Partitioned with schema
danube-admin topics create /default/orders \
  --partitions 5 \
  --schema-subject order-events \
  --dispatch-strategy reliable

Option	Description	Default
`--namespace`	Namespace (if not in topic path)	—
`--partitions`	Number of partitions	`1`
`--schema-subject`	Schema subject from registry	None
`--dispatch-strategy`	`reliable` or `non_reliable`	`non_reliable`

Dispatch strategies:

Strategy	Delivery	Use Case
`non_reliable`	At-most-once (fire-and-forget)	Logs, metrics, non-critical events
`reliable`	At-least-once (with acknowledgments)	Transactions, orders, critical events

Describe Topic

danube-admin topics describe /default/user-events

Topic: /default/user-events
Broker ID: broker-001
Delivery: Reliable

📋 Schema Registry:
  Subject: user-events
  Schema ID: 12345
  Version: 2
  Type: json_schema
  Compatibility: BACKWARD

Subscriptions: ["analytics-consumer", "audit-logger"]

List Subscriptions

danube-admin topics subscriptions /default/orders

Delete Topic

danube-admin topics delete /default/old-topic

Unsubscribe

danube-admin topics unsubscribe /default/events --subscription old-consumer

Unload Topic (Reassign)

danube-admin topics unload /default/events

Dispatch Configuration (Per-Subscription)

# Set pipelining depth
danube-admin topics set-dispatch-config /default/orders \
  --subscription order-workers \
  --max-unacked-messages 50

# Read current setting
danube-admin topics get-dispatch-config /default/orders \
  --subscription order-workers

Topic Schema Configuration (Admin-Only)

These commands control schema enforcement at the topic level.

Configure Topic Schema

danube-admin topics configure-schema /production/orders \
  --subject order-events \
  --validation-policy enforce \
  --enable-payload-validation

Option	Values	Description
`--subject`	String	Schema subject from registry
`--validation-policy`	`none`, `warn`, `enforce`	Validation strictness
`--enable-payload-validation`	Flag	Enable deep payload validation

Set Validation Policy

# Warn mode (for debugging)
danube-admin topics set-validation-policy /production/orders \
  --policy warn --enable-payload-validation

# Enforce (production)
danube-admin topics set-validation-policy /production/orders \
  --policy enforce --enable-payload-validation

# Disable
danube-admin topics set-validation-policy /production/orders \
  --policy none

Policy	Behavior
`none`	No validation
`warn`	Validate and log errors, accept messages
`enforce`	Reject invalid messages

Get Schema Configuration

danube-admin topics get-schema-config /production/orders

Full Topic + Schema Workflow

# 1. Register schema
danube-admin schemas register order-events \
  --schema-type json_schema \
  --file schemas/orders.json \
  --description "Order transaction schema"

# 2. Set compatibility mode
danube-admin schemas set-compatibility order-events --mode backward

# 3. Create topic
danube-admin topics create /production/orders \
  --dispatch-strategy reliable --partitions 5

# 4. Configure schema with strict validation
danube-admin topics configure-schema /production/orders \
  --subject order-events \
  --validation-policy enforce \
  --enable-payload-validation

# 5. Verify
danube-admin topics describe /production/orders
danube-admin topics get-schema-config /production/orders

Schemas

Register

danube-admin schemas register user-events \
  --schema-type json_schema \
  --file schemas/user-events.json \
  --description "User event schema" \
  --tags users analytics

Type	Description
`json_schema`	JSON Schema (Draft 7)
`avro`	Apache Avro
`protobuf`	Protocol Buffers
`string`	Plain text
`bytes`	Raw bytes

Get Schema

# By subject (latest version)
danube-admin schemas get --subject user-events

# By schema ID
danube-admin schemas get --id 12345

# JSON output
danube-admin schemas get --subject user-events --output json

List Versions

danube-admin schemas versions user-events

Check Compatibility

danube-admin schemas check user-events \
  --file schemas/user-events-v2.json \
  --schema-type json_schema

Set Compatibility Mode

danube-admin schemas get-compatibility user-events
danube-admin schemas set-compatibility user-events --mode backward

Mode	Description
`none`	No checks
`backward`	New schema reads old data (default)
`forward`	Old schema reads new data
`full`	Both backward and forward

Delete Version

danube-admin schemas delete user-events --version 1 --confirm

Schema Evolution Workflow

# 1. Check current schema and compatibility
danube-admin schemas get --subject user-events
danube-admin schemas get-compatibility user-events

# 2. Check compatibility of new version
danube-admin schemas check user-events \
  --file schemas/user-events-v2.json \
  --schema-type json_schema

# 3. Register if compatible
danube-admin schemas register user-events \
  --schema-type json_schema \
  --file schemas/user-events-v2.json \
  --description "Added email field"

# 4. Verify
danube-admin schemas versions user-events

Common Workflows

Health Check

danube-admin cluster status      # Raft state
danube-admin brokers list        # All brokers
danube-admin brokers leader      # Current leader
danube-admin brokers balance     # Load distribution

Broker Maintenance

# 1. Preview drain
danube-admin brokers unload broker-001 --dry-run

# 2. Drain topics
danube-admin brokers unload broker-001

# 3. Perform maintenance

# 4. Reactivate
danube-admin brokers activate broker-001 --reason "Maintenance completed"

# 5. Rebalance if needed
danube-admin brokers balance
danube-admin brokers rebalance --dry-run

Danube Admin

File contents