Run any Skill in Manus with one click

inlined-refs

Stars39

Forks3

UpdatedMay 29, 2026 at 20:32

Generate a Kafka consumer group lag dashboard. Use when the user asks to monitor lag, build a dashboard for consumer lag, or wire up Prometheus exporters for Kafka. Do NOT trigger for producer metrics, broker JMX, or Streams-specific monitoring.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

confluentinc

confluentinc/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	inlined-refs
description	Generate a Kafka consumer group lag dashboard. Use when the user asks to monitor lag, build a dashboard for consumer lag, or wire up Prometheus exporters for Kafka. Do NOT trigger for producer metrics, broker JMX, or Streams-specific monitoring.

inlined-refs — consumer lag dashboarding

Step 1 — pick the exporter

We support two exporters. Read the comparison below before recommending.

Exporter comparison (from references/exporters.md)

kafka-exporter (Danielqsj)

Pros: lightweight, single binary, exposes per-group lag directly. Cons: stateful (consumes __consumer_offsets internally), can lag on large clusters.

Best for: clusters < 100 brokers, < 1000 consumer groups.

Config snippet:

kafka-exporter \
  --kafka.server=localhost:9092 \
  --kafka.version=3.5.0 \
  --web.listen-address=:9308

Confluent Control Center

Pros: official, covers full Confluent Platform metrics. Cons: paid licensing, heavier footprint.

Best for: enterprise Confluent Platform users.

Step 2 — Grafana dashboard

Use Grafana dashboard 7589 for kafka-exporter. Filter by consumer group, plot kafka_consumergroup_lag over a 5-minute window.

Step 3 — alerts

Set lag > 10,000 messages for 5 minutes as the default alert. Adjust per topic SLA.

More from this repository

same repository

confluent-cloud-cdc-tableflow

confluentinc/agent-skills

Set up end-to-end Change Data Capture (CDC) pipelines on Confluent Cloud using Debezium source connectors, Flink for transformation, and Tableflow for data lake integration. Supports JSON_SR, Avro, and Protobuf formats. Handles schemaless topics (plain JSON without SR) and multi-event topics. This skill handles the complete workflow from database to Iceberg/Delta tables. Use this skill when users want to capture database changes and materialize them into Iceberg or Delta Lake tables via Confluent Cloud Tableflow. Trigger phrases include "CDC to Tableflow", "database to Iceberg", "database to Delta Lake", "stream database changes to data lake", "set up Tableflow pipeline", "schemaless topic to Tableflow", or "multi-event topic to Iceberg". Do NOT trigger for general CDC, Debezium, or database replication requests that do not involve Tableflow or Iceberg/Delta Lake as the destination.

2026-07-0639

confluent-skill-creator

confluentinc/agent-skills

Create Confluent-specific skills for external users. Use this skill when users want to create, build, or author a new skill related to Confluent Cloud, Confluent Platform, Apache Kafka, WarpStream, Flink, Connectors, Schema Registry, Tableflow, CDC pipelines, or any Confluent product. Skills can be use-case focused (like data enrichment, CDC to Tableflow, stream processing workflows) or component-specific (like a Flink skill, Schema Registry skill, or Connector skill). Do NOT use this skill when users want to directly use Confluent products (e.g., build a pipeline, write a producer, deploy Flink SQL) — use the appropriate product-specific skill instead. This skill is specifically for creating new skills, not for using existing ones.

2026-07-0639

confluent-skill-reviewer

confluentinc/agent-skills

Review a Confluent agent skill in this repo against the Agent Skills spec (agentskills.io), Confluent conventions in CLAUDE.md, the PR template gates, and the evals-as-contract rule. Use this skill whenever the user asks to review, audit, validate, or lint a skill; opens or inspects a PR that adds or modifies anything under `skills/`; asks about spec conformance, lazy-loading, frontmatter shape, trigger overlap, or eval coverage; or wants a pre-merge sanity check on skill changes. Do NOT trigger for general code review of application code; security review; auditing schemas, producer/consumer configs, PII tagging, or Terraform generation for Schema Registry (handled by `kafka-schema-registry`); runtime/log analysis of skill behavior (use `tools/skill_review_dashboard.py`); or any changes that don't touch the `skills/` tree.

2026-07-0639

developing-kafka-python-client

confluentinc/agent-skills

Use when the user wants to build a Python Kafka producer or consumer, add Schema Registry to existing Python code, migrate from raw JSON to schema-backed serialization, or scaffold a confluent-kafka-python project for Confluent Cloud, local Docker, or WarpStream. Also use when user wants to optimize Python Kafka client configuration for WarpStream.

2026-07-0639

flink-udf

confluentinc/agent-skills

Build and deploy Apache Flink user-defined functions (UDFs) in Java for stream processing over Kafka. Use this skill when users want to create scalar UDFs, user-defined table functions (UDTFs), or process table functions (PTFs) in Java, deploy them to Confluent Cloud or local Docker environments, and invoke them from Flink SQL or the Table API. Trigger on: Flink UDF, custom Flink function, process table function, PTF, UDTF, Flink user defined, extend Flink SQL, stateful stream processing with Flink. Do NOT trigger for: Kafka Streams UDFs (use kafka-streams-programming skill), general Flink job development without custom functions, CDC streaming data piplines that include Flink (prefer the confluent-cloud-cdc-tableflow skill), Flink connector setup, or Kafka producer/consumer code.

2026-07-0639

kafka-schema-registry

confluentinc/agent-skills

Scan a project to identify Kafka applications, extract schemas from data models, tag PII fields, generate Terraform for Confluent Schema Registry registration, and produce a migration report with rollout ordering. Use this skill when a user asks to analyze a folder or repo for Kafka usage, extract schemas, audit producer/consumer configurations, or generate Terraform for Schema Registry.

2026-07-0639

name	inlined-refs
description	Generate a Kafka consumer group lag dashboard. Use when the user asks to monitor lag, build a dashboard for consumer lag, or wire up Prometheus exporters for Kafka. Do NOT trigger for producer metrics, broker JMX, or Streams-specific monitoring.

inlined-refs — consumer lag dashboarding

Step 1 — pick the exporter

We support two exporters. Read the comparison below before recommending.

Exporter comparison (from references/exporters.md)

kafka-exporter (Danielqsj)

Pros: lightweight, single binary, exposes per-group lag directly. Cons: stateful (consumes __consumer_offsets internally), can lag on large clusters.

Best for: clusters < 100 brokers, < 1000 consumer groups.

Config snippet:

kafka-exporter \
  --kafka.server=localhost:9092 \
  --kafka.version=3.5.0 \
  --web.listen-address=:9308

Confluent Control Center

Pros: official, covers full Confluent Platform metrics. Cons: paid licensing, heavier footprint.

Best for: enterprise Confluent Platform users.

Step 2 — Grafana dashboard

Use Grafana dashboard 7589 for kafka-exporter. Filter by consumer group, plot kafka_consumergroup_lag over a 5-minute window.

Step 3 — alerts

Set lag > 10,000 messages for 5 minutes as the default alert. Adjust per topic SLA.