Topics List

Before starting: If any tool call fails with "Missing required environment variables", tell the user: "Set your Confluent Cloud API credentials — generate at https://confluent.cloud/settings/api-keys, then export CONFLUENT_CLOUD_API_KEY=... CONFLUENT_CLOUD_API_SECRET=... and restart Claude Code."

List all topics in a Kafka cluster.

Resolve environment — First, read the file .confluent-context.json in the project root. If it exists and contains an environment_id, use that environment automatically and tell me: "Using active environment {name} ({id}). Run /environments-use to change." If the file doesn't exist or has no environment set, call list_environments and ask me to pick one.
Pick cluster — Call list_clusters for the chosen environment. Ask me to pick a cluster.
Get cluster API key — First, check .confluent-context.json for a stored API key for this cluster (under api_keys[cluster_id]). If found, use it automatically and tell me: "Using stored API key {api_key} for cluster {cluster_id}." If no stored key is found, call list_api_keys with the cluster's resource_id to check for existing keys.
- If keys exist, offer to create a new one with create_api_key (credentials are saved automatically).
- If no keys exist, offer to create one with create_api_key. Credentials are saved automatically to context.
List topics — Call list_topics with the cluster ID, environment ID, and cluster API credentials.
Present results — Show topics as a table:

Topic Name Partitions
If no topics exist, suggest creating one with /topics-create.

List all topics in a Kafka cluster.

Resolve environment — First, read the file .confluent-context.json in the project root. If it exists and contains an environment_id, use that environment automatically and tell me: "Using active environment {name} ({id}). Run /environments-use to change." If the file doesn't exist or has no environment set, call list_environments and ask me to pick one.
Pick cluster — Call list_clusters for the chosen environment. Ask me to pick a cluster.
Get cluster API key — First, check .confluent-context.json for a stored API key for this cluster (under api_keys[cluster_id]). If found, use it automatically and tell me: "Using stored API key {api_key} for cluster {cluster_id}." If no stored key is found, call list_api_keys with the cluster's resource_id to check for existing keys.
- If keys exist, offer to create a new one with create_api_key (credentials are saved automatically).
- If no keys exist, offer to create one with create_api_key. Credentials are saved automatically to context.
List topics — Call list_topics with the cluster ID, environment ID, and cluster API credentials.
Present results — Show topics as a table:

Topic Name Partitions
If no topics exist, suggest creating one with /topics-create.

Topics List

Additional Files (15)

Related Skills

<h1 align="center">

Frontend Typescript Linting.mdc

2. Apply Deepthink Protocol (reason about dependencies

Additional Files (15)