ClawHub

Kafka

v3.0.1

Produce, consume, and manage Kafka topics with lag monitoring and data export. Use when publishing messages, consuming topics, monitoring consumer lag.

⭐ 0· 327·1 current·1 all-time
byBytesAgain2@ckchzh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the implementation: the script invokes standard kafka-*.sh CLI tools to list/create/describ e/produce/consume, manage partitions and consumer groups, and report lag. Optional environment variables the script honors (KAFKA_BOOTSTRAP, KAFKA_ZOOKEEPER, KAFKA_HOME, KAFKA_CONFIG_FILE) are appropriate for configuring Kafka access.
ℹ
Instruction Scope
SKILL.md instructs invoking scripts/script.sh for all operations, which is consistent with the included script. Minor mismatch: the registry metadata lists no required env vars but the script reads optional env vars (KAFKA_BOOTSTRAP, KAFKA_ZOOKEEPER, KAFKA_HOME, KAFKA_CONFIG_FILE); these are reasonable for configuring Kafka but users should be aware they control the script's targets. The script writes a local data dir (~/.local/share/kafka-helper) and log file.
✓
Install Mechanism
No install spec — instruction-only skill with an included helper script. It does not download code at runtime or fetch external archives. Risk is limited to executing the included shell script and the local Kafka CLI tools it calls.
ℹ
Credentials
The skill does not require credentials from the registry metadata. It optionally uses KAFKA_CONFIG_FILE which may contain connection/security settings (e.g., SASL/SSL configs) — this is proportional to connecting to secured Kafka clusters but users should ensure any config file referenced is trusted. No unrelated service tokens or secrets are requested.
✓
Persistence & Privilege
The skill is not always-enabled and does not modify other skills or global agent settings. It creates a per-user data directory and log file under $HOME, which is expected for a CLI helper and is not an elevated privilege.
Assessment
This skill appears to do what it says: it wraps your local Kafka CLI tools. Before installing/using it: (1) ensure you have the kafka-*.sh CLI tools available or install Kafka; (2) inspect scripts/script.sh yourself (it will create ~/.local/share/kafka-helper and a log file) and confirm you trust it; (3) if connecting to a secured Kafka cluster, be careful with KAFKA_CONFIG_FILE — it can contain credentials or TLS settings, so point it to a safe config; (4) run the script in a controlled environment (or with non-production Kafka) the first time to confirm behavior. If you want tighter control, set explicit KAFKA_BOOTSTRAP/KAFKA_HOME rather than relying on defaults or global config files.

Like a lobster shell, security has layers — review code before you run it.

latestvk970kfx70yz85q8svqkdvcmjys837w8r

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments