New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Rocketmq Rust Local Cluster

by mxsm in mxsm/rocketmq-rust

Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout.

Apache-2.0Auto-check passedDevOps & Cloud

Install Rocketmq Rust Local Cluster

skills CLI
$ npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-local-cluster -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mxsm/rocketmq-rust rocketmq-rust-local-cluster --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mxsm/rocketmq-rust.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/rocketmq-rust-local-cluster .claude/skills/rocketmq-rust-local-cluster && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rocketmq-rust-local-cluster
GitHub stars
1.5k
Token cost
~2k tokens
SKILL.md length
830 words
Files
7 (incl. scripts, references)
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout.

  • Works in 5 steps: Read applicable AGENTS.md instructions… → Generate configuration and a run… → Follow operations and lifecycle: build… → …
  • Single-Broker development
  • SKILL.md covers Select a topology, Workflow, Configuration helper and Execution boundaries, plus 1 more section
  • Runs Python scripts from its folder; calls git

What it does

Rocketmq Rust Local Cluster is an agent skill from mxsm/rocketmq-rust. Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout. Use for single-Broker development, replicated master/slave clusters, Proxy cluster/local mode, or three-node Controller HA with automatic Broker election.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/operations.md` and `references/topologies.md`).

It sits in DevOps & Cloud. It works with Rust and Model Context Protocol. The repository describes itself as: 🚀 Apache RocketMQ built in Rust 🦀 — faster, safer, and more memory-efficient. Powering high-performance messaging for the AI era, with AI Agent, MCP, and AI-SRE capabilities. The licence is Apache-2.0.

When your agent uses it

  • Single-Broker development
  • Replicated master/slave clusters
  • Proxy cluster/local mode
  • Three-node Controller HA with automatic Broker election

Example prompts

  • “/rocketmq-rust-local-cluster”

Requirements

  • Python 3
  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read applicable AGENTS.md instructions and git status --short. Inspect OS, toolchain, disk capacity, and port occupancy. Keep the selected…
  2. Generate configuration and a run manifest with the helper below. It writes files and optionally probes port availability; it does not…
  3. Follow operations and lifecycle: build the necessary binaries, check configuration parsing, record process ownership, start dependency…
  4. Follow verification and troubleshooting: check registration and a message round trip. For HA, inspect replication/election state. Perform…
  5. Deliver the actual endpoints, configuration/data/log locations, verification results, and reusable start/status/stop commands. Leave the…

What it can do on your machine

Read from SKILL.md and the folder at commit b838c69. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rocketmq Rust Local Cluster loads about 2k tokens when it runs, and up to ~8.4k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 830 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mxsm/rocketmq-rust at commit b838c69, republished under its Apache-2.0 licence (© mxsm). 830 words, ~2,046 tokens.

Download SKILL.mdSave it as .claude/skills/rocketmq-rust-local-cluster/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
rocketmq-rust-local-cluster
description
Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout. Use for single-Broker development, replicated master/slave clusters, Proxy cluster/local mode, or three-node Controller HA with automatic Broker election.

RocketMQ Rust Local Cluster

Turn the requested topology into a running, verifiable local environment with isolated data and an explicit stop procedure. Use this checkout's manifests, configuration parsers, and entrypoints. Java RocketMQ scripts and old flat Broker configuration are not substitutes for the Rust services.

Select a topology

Preserve the user's topology, paths, ports, and execution method. Otherwise default to dev-single, native processes, loopback addresses, and a debug build; state the assumptions and continue. For an unspecified request for HA, select controller-ha and explain its larger resource needs. Select dev-ha when the user explicitly wants ordinary master/slave replication.

ProfileProcessesPurpose and limits
dev-single1 NameServer + 1 BrokerMinimum message round trip; no replica
dev-ha2 NameServers + 1 master + 1 slaveSynchronous replication by default; no automatic writable-master promotion
dev-ha-2m2s2 NameServers + 2 master/slave groupsTwo distinct brokerName values; ordinary replication
proxy-clusterdev-single + a separate ProxygRPC ingress forwarding to the backend cluster
proxy-local1 Proxy with an embedded BrokerSingle-process development; no separate NameServer/Broker and no HA
controller-ha2 NameServers + 3 Controllers + 3 Brokers in one groupRaft quorum, automatic Broker election, and replica synchronization

--with-proxy adds a separate Proxy to dev-single, dev-ha, dev-ha-2m2s, or controller-ha. It adds one ingress instance; Proxy redundancy needs additional instances and an endpoint strategy when requested.

These are single-host development topologies. They do not survive loss of the host or its disks. Explain synchronous replication (SYNC_MASTER), disk flush (SYNC_FLUSH), and automatic election as separate properties.

Workflow

For status, stop, or restart requests, open the existing environment manifest and process records first. Skip configuration generation and builds unless a requested restart actually needs updated binaries. Do not create another cluster while inspecting an existing one.

  1. Read applicable AGENTS.md instructions and git status --short. Inspect OS, toolchain, disk capacity, and port occupancy. Keep the selected Rust toolchain. Use topology rules and source map to check only the requested components.
  2. Generate configuration and a run manifest with the helper below. It writes files and optionally probes port availability; it does not compile, start processes, or delete data. Stop at artifacts if the user requested only a plan/configuration; continue through startup and verification when asked to set up an environment.
  3. Follow operations and lifecycle: build the necessary binaries, check configuration parsing, record process ownership, start dependency groups, and wait for readiness within a deadline. Initial compilation can dominate setup time; report actual progress.
  4. Follow verification and troubleshooting: check registration and a message round trip. For HA, inspect replication/election state. Perform disruptive failover exercises when requested, then restore the environment.
  5. Deliver the actual endpoints, configuration/data/log locations, verification results, and reusable start/status/stop commands. Leave the environment running when that is the requested outcome. Report the last completed stage on failure; generated configuration is not successful startup.
Show full SKILL.md (368 more words)Show less

Configuration helper

Run from the repository root using Python 3.11+. On Linux/macOS, python3 may replace python. When using the Claude copy, replace the script prefix with .claude/skills.

text
python .agents/skills/rocketmq-rust-local-cluster/scripts/prepare_cluster.py --name dev --profile dev-single --check-ports
python .agents/skills/rocketmq-rust-local-cluster/scripts/prepare_cluster.py --name ha --profile dev-ha --port-offset 1000 --check-ports
python .agents/skills/rocketmq-rust-local-cluster/scripts/prepare_cluster.py --name dual --profile dev-ha-2m2s --replication async --port-offset 2000
python .agents/skills/rocketmq-rust-local-cluster/scripts/prepare_cluster.py --name proxy --profile proxy-cluster --port-offset 3000
python .agents/skills/rocketmq-rust-local-cluster/scripts/prepare_cluster.py --name local --profile proxy-local --port-offset 4000
python .agents/skills/rocketmq-rust-local-cluster/scripts/prepare_cluster.py --name controller --profile controller-ha --with-proxy --port-offset 5000 --check-ports
  • Output defaults to ignored .rocketmq/clusters/<name>/. Use --repo-root for another checkout or --output for a new, dedicated environment directory.
  • --dry-run prints the manifest without writing files. --check-ports checks whether all planned loopback ports can currently bind; it does not reserve them for startup.
  • Existing output directories are rejected to preserve configuration and messages. For restart/status/stop, read the existing manifest.json. Prefer a new environment for topology changes.
  • --replication async applies only to ordinary HA profiles. Controller HA retains three replicas and a minimum of two in-sync replicas; do not lower write requirements to conceal startup or replication failures.
  • Add --proxy-remoting only when Remoting ingress is requested. The default Proxy ingress is gRPC.
  • Base ports: NameServer 9876/9886; Broker remoting 10911 + 20*i, fast channel remoting - 2, HA remoting + 1; Controller remoting 9878/9888/9898, Raft 9879/9889/9899; Proxy gRPC 8081, optional remoting 8080; health 18000 + node index. --port-offset shifts all ports and their references together.

Execution boundaries

  • A request to set up the environment authorizes necessary local configuration, builds, startup, and non-disruptive verification without repeated confirmation. It does not authorize publication, remote-cluster changes, system services, or deleting old data.
  • The native generator uses 127.0.0.1 and development-insecure-loopback. Inspect conflicting inherited TLS/ACL or listener environment settings; resolve them only for these new processes. Preserve security settings of existing environments.
  • On port conflicts, choose another offset or the user's available ports. Do not terminate the current port owner. Isolate every instance's persistence and logs instead of using a shared default home-directory store.
  • Record PID, process creation time, executable path, arguments, and configuration path. Verify identity before stopping; a process name or stale PID file alone is insufficient.
  • Preserve data by default. For an explicitly requested reset, first resolve absolute paths, verify they remain in this environment and do not link elsewhere, and stop its processes. Delete only that environment's intended data.
  • Docker/Compose, WSL, and local Kubernetes are optional execution methods. Use the container branch when requested; native loopback configuration cannot be mounted unchanged into multiple containers. Local setup does not require release, performance, full-workspace Clippy, or integration fault-matrix gates.

Example requests

text
Use $rocketmq-rust-local-cluster to start a minimal development cluster and verify one message round trip.
Use $rocketmq-rust-local-cluster to create an asynchronous two-master/two-slave environment with port offset 2000, preserving my existing cluster.
Use $rocketmq-rust-local-cluster to start Controller HA with Proxy and verify message delivery after automatic failover.
Use $rocketmq-rust-local-cluster to inspect the dev environment, then stop it while preserving messages.

© mxsm, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in .agents/skills/rocketmq-rust-local-cluster of mxsm/rocketmq-rust.

  • SKILL.md
  • agents/openai.yaml
  • references/operations.md
  • references/topologies.md
  • references/verification.md
  • scripts/prepare_cluster.py
  • scripts/test_prepare_cluster.py

Open the folder on GitHubat commit b838c69

Compare with similar skills

Rocketmq Rust Local Cluster next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rocketmq Rust Local Cluster compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rocketmq Rust Local Cluster this skillmxsm/rocketmq-rust1.5k—~2kAutomated safety check: PassApache-2.0
Syncmetapawurb/hotpath-rs1.9k—~1.2kAutomated safety check: NotesMIT
Monitoring Capture ServicePostHog/posthog40k—~5kAutomated safety check: PassCustom licence
Reviewapollographql/apollo-mcp-server311—~2.9kAutomated safety check: PassMIT
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT

Similar skills

  • Syncmeta

    pawurb/hotpath-rs

    Sync changes from the hotpath, hotpath-macros and hotpath-drain crates to their meta counterparts (hotpath-meta, hotpath-macros-meta and hotpath-drain-meta).

    1.9k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Monitoring Capture Service

    PostHog/posthog

    Official

    Guide for using the Grafana MCP to monitor and diagnose the capture service (rust/capture) in production.

    40k GitHub stars~5k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Review

    apollographql/apollo-mcp-server

    Review a GitHub pull request for a Rust codebase. An agent skill from apollographql/apollo-mcp-server.

    311 GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from mxsm/rocketmq-rust

  • Rocketmq Rust Issue Generator

    mxsm/rocketmq-rust

    A skill your agent uses when the user asks to create, draft, prepare, or publish a GitHub issue for the rocketmq-rust project — bugs, features, enhancements, refactors, docs, unit tests, CI…

    1.5k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Rocketmq Rust PR Submitter

    mxsm/rocketmq-rust

    A skill your agent uses when the user asks to prepare, submit, publish, or optimize a pull request for the rocketmq-rust project, especially when the PR title or commit message must follow the [ISSUE

    1.5k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Translate It Doc En Zh

    mxsm/rocketmq-rust

    Translate English IT and software engineering documents into professional, accurate Chinese.

    1.5k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Rocketmq Rust Good First Issue

    mxsm/rocketmq-rust

    Help the rocketmq-rust repository owner or maintainer prepare and publish good first issues for new contributors to claim, with exact files, concrete changes, acceptance criteria, labels, and…

    1.5k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Rust Doc Comment Generator

    mxsm/rocketmq-rust

    Generate idiomatic, production-grade Rust comments and documentation strictly following official Rustdoc and Rust API documentation conventions.

    1.5k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Rocketmq Rust Local Cluster

What does Rocketmq Rust Local Cluster do?

Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout. Rocketmq Rust Local Cluster is an agent skill from mxsm/rocketmq-rust. Set up, start, verify, inspect, and stop local development clusters from the current rocketmq-rust checkout.

When should I use Rocketmq Rust Local Cluster?

Rocketmq Rust Local Cluster fits situations like: single-Broker development; replicated master/slave clusters; proxy cluster/local mode; three-node Controller HA with automatic Broker election.

How do I install Rocketmq Rust Local Cluster in Claude Code?

Run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-local-cluster -a claude-code`. Or copy the skill folder (.agents/skills/rocketmq-rust-local-cluster in mxsm/rocketmq-rust) into .claude/skills/rocketmq-rust-local-cluster in your project. Claude Code loads it when a task matches its description.

How do I install Rocketmq Rust Local Cluster in Codex?

Run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-local-cluster -a codex`. Or copy the skill folder (.agents/skills/rocketmq-rust-local-cluster in mxsm/rocketmq-rust) into .agents/skills/rocketmq-rust-local-cluster in your project. Codex loads it when a task matches its description.

Can I use Rocketmq Rust Local Cluster in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mxsm/rocketmq-rust --skill rocketmq-rust-local-cluster -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rocketmq-rust-local-cluster, .gemini/skills/rocketmq-rust-local-cluster, .github/skills/rocketmq-rust-local-cluster and .opencode/skills/rocketmq-rust-local-cluster in your project.

What does Rocketmq Rust Local Cluster need to run?

Going by SKILL.md and its folder, Rocketmq Rust Local Cluster needs Python for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: Python 3; Docker.

Does Rocketmq Rust Local Cluster access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Rocketmq Rust Local Cluster safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Rocketmq Rust Local Cluster use?

Rocketmq Rust Local Cluster is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rocketmq Rust Local Cluster use?

About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.4k tokens, read only when the agent opens those files.

What are the alternatives to Rocketmq Rust Local Cluster?

Skills that share tags, products or a category with Rocketmq Rust Local Cluster: Syncmeta (pawurb/hotpath-rs, 1.9k stars), Monitoring Capture Service (PostHog/posthog, 40k stars), Review (apollographql/apollo-mcp-server, 311 stars) and GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rocketmq Rust Local Cluster?

mxsm (a GitHub user) maintains it in mxsm/rocketmq-rust, which has 1,522 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.

Source: mxsm/rocketmq-rust on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.