good-skill

Generate idempotent Confluent Cloud topic creation scripts using the confluent CLI.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill good-skill-ricardolui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: good-skill
Source: https://github.com/ricardolui/gcp-custom-agent-skills/tree/main/confluent-skill-reviewer/evals/mock-skills/good-skill
Command: npx skills add https://github.com/ricardolui/gcp-custom-agent-skills --skill good-skill-ricardolui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually writing Confluent Cloud topic provisioning scripts is error-prone and often lacks idempotency, causing failures when scripts are re-run. This Skill generates a create-topics.sh script with built-in existence checks so topics can be provisioned safely and repeatedly. ## Core Features & Use Cases - Idempotent Script Generation: Produces create-topics.sh using confluent kafka topic create with a confluent kafka topic list check before each create. - Lazy-Loaded References: Routes sizing questions to partition-count guidance and authentication questions to Cloud API key instructions only when needed. - Scope Guardrails: Confirms the user is on Confluent Cloud and hands off self-managed Apache Kafka, schema registry, Terraform, and Kafka Streams requests. - Use Case: A developer needs to provision orders, payments, and refunds topics on a Basic cluster at ~20 MB/s; the Skill generates a script with 6 partitions per topic and idempotent creates. ## Quick Start Ask the assistant to generate a create-topics.sh script for your Confluent Cloud cluster with your topic names, partition counts, and replication factor.

Frequently Asked Questions about good-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Kafka topics on Confluent Cloud with a script?

Use the confluent CLI command `confluent kafka topic create --cluster <cluster-id>` inside a generated create-topics.sh script. The script checks `confluent kafka topic list` before each create so re-running it does not fail on existing topics.

How many partitions should a Confluent Cloud Basic topic have?

For Basic clusters, default to 6 partitions per topic for throughput up to 50 MB/s and scale to 12 partitions for 100 MB/s. Higher throughput requirements need a Dedicated cluster.

How do I authenticate the confluent CLI to Confluent Cloud?

Run `confluent api-key create --resource <cluster-id>` to generate Kafka API keys. Store the key and secret in a `.env` file and never commit them to version control.

Does this work with self-managed Apache Kafka clusters?

No, the workflow is scoped to Confluent Cloud only and hands off self-managed Apache Kafka requests. It also excludes schema registration, Terraform generation, and Kafka Streams topology authoring.

Why use confluent CLI instead of kafka-topics.sh for topic creation?

The confluent CLI targets Confluent Cloud clusters directly with Cloud API key authentication, while kafka-topics.sh is designed for self-managed brokers via bootstrap servers. Cloud provisioning requires the confluent CLI commands.