القائمة
Kafka topic and consumer group management. Use when investigating Kafka topics, consumer lag, broker health, or consumer group status.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Pull incident context from alerting platforms (PagerDuty). Use when investigating who's on-call, incident history, alert patterns, or MTTR metrics.
Opsgenie alert management and on-call scheduling. Use for listing alerts, checking on-call, computing MTTA/MTTR, and alert fatigue analysis. Supports team and priority filtering.
Amplitude product analytics. Use when querying user events, funnels, retention, or product usage data. Provides event segmentation, user activity lookup, and annotation queries.
Google BigQuery data warehouse queries and schema inspection. Use when running SQL queries, listing datasets/tables, or inspecting table schemas in BigQuery.
MySQL/MariaDB database inspection and queries. Use when investigating table schemas, running queries, checking processlist, replication status, InnoDB engine status, or lock contention.
PostgreSQL database inspection and queries. Use when investigating table schemas, running queries, checking locks, replication status, or long-running queries.
| name | streaming-kafka |
| description | Kafka topic and consumer group management. Use when investigating Kafka topics, consumer lag, broker health, or consumer group status. |
| allowed-tools | Bash(python *) |
IMPORTANT: Credentials are injected automatically by a proxy layer. Do NOT check for KAFKA_SASL_PASSWORD in environment variables - it won't be visible to you. Just run the scripts directly; authentication is handled transparently.
Configuration environment variables you CAN check (non-secret):
KAFKA_BOOTSTRAP_SERVERS - Kafka broker addressesKAFKA_SECURITY_PROTOCOL - Security protocol (PLAINTEXT, SSL, SASL_SSL, SASL_PLAINTEXT)Start with broker info, then check topics and consumer groups.
BROKER INFO → LIST TOPICS → DESCRIBE TOPIC → CHECK CONSUMER LAG
All scripts are in .claude/skills/streaming-kafka/scripts/
python .claude/skills/streaming-kafka/scripts/get_broker_info.py
python .claude/skills/streaming-kafka/scripts/list_topics.py [--include-internal]
python .claude/skills/streaming-kafka/scripts/describe_topic.py --topic TOPIC_NAME
python .claude/skills/streaming-kafka/scripts/list_consumer_groups.py
python .claude/skills/streaming-kafka/scripts/describe_consumer_group.py --group GROUP_ID
python .claude/skills/streaming-kafka/scripts/get_consumer_lag.py --group GROUP_ID [--topic TOPIC]
| Total Lag | Health |
|---|---|
| 0 | healthy |
| < 1,000 | minor_lag |
| < 100,000 | lagging |
| >= 100,000 | severely_lagging |
1. get_broker_info.py (verify cluster health)
2. list_consumer_groups.py (find the group)
3. get_consumer_lag.py --group <group-id> (check lag)
4. describe_topic.py --topic <topic> (check partition details)
1. list_topics.py
2. describe_topic.py --topic <topic> (partitions, configs, offsets)
3. Check under-replicated partitions in output