CtrlK
BlogDocsLog inGet started
Tessl Logo

good-skill

Generate a Confluent Cloud topic creation script with idempotency checks. Use when the user asks to create a topic, provision topics, or write a `create-topics.sh` for Confluent Cloud. Do NOT trigger for self-managed Apache Kafka, schema registration, Terraform generation, or Kafka Streams topology authoring.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a concise, well-structured overview that lazy-loads references with clear routing and includes an idempotency validation checkpoint in its workflow. It could improve actionability by showing a complete executable script example and an explicit error-recovery loop for the batch create operation.

Suggestions

Include a complete, copy-paste-ready `create-topics.sh` example (with real flag values) rather than only templated command fragments.

Add an explicit error-recovery feedback loop after the idempotency check (e.g., if a topic exists or creation fails, report and continue/skip) to raise workflow clarity for the batch operation.

Specify the auth/key prerequisites inline or clearly route to `references/auth.md` from the steps, since `confluent kafka topic create` requires authenticated API keys not mentioned in the step sequence.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining what Confluent Cloud or Kafka is; every line (steps, idempotency, reference routing) earns its place.

5 / 5

Actionability

It gives concrete commands (`confluent kafka topic create --cluster ...`, `confluent kafka topic list`) but they are templated with placeholders and no complete copy-paste `create-topics.sh` example is provided, leaving minor gaps.

4 / 5

Workflow Clarity

Five numbered steps form a clear sequence and step 4 supplies a validation checkpoint (check `topic list` before each create), but there is no explicit error-recovery feedback loop for the batch operation.

4 / 5

Progressive Disclosure

The overview routes to two real one-level-deep references (`references/sizing.md`, `references/auth.md`) with explicit per-question navigation, and sizing/auth detail is appropriately split out rather than inlined.

5 / 5

Total

18

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong overall: it answers both what and when explicitly, uses natural trigger terms with synonyms, and carves out a distinct niche with explicit negative triggers. The only modest gap is that it describes one core action rather than enumerating several specific capabilities.

DimensionReasoningScore

Specificity

"Generate a Confluent Cloud topic creation script with idempotency checks" names the domain and one main action with a modifier, but does not list several specific concrete actions for comprehensive coverage.

3 / 5

Completeness

It clearly states what it does (generate a topic creation script with idempotency) and explicitly when to use it via a "Use when..." clause with concrete trigger phrases, plus negative triggers.

5 / 5

Trigger Term Quality

"create a topic, provision topics, or write a `create-topics.sh`" provides good natural-phrase coverage with synonyms (create/provision), though a few common variations are absent.

4 / 5

Distinctiveness Conflict Risk

The Confluent Cloud topic-provisioning niche is sharply bounded by the explicit "Do NOT trigger for self-managed Apache Kafka, schema registration, Terraform generation, or Kafka Streams" exclusions, minimizing conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
confluentinc/agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.