trigger-overlap

Build a Confluent Cloud topic provisioning script with retention and compaction. Use when the user asks to create a topic, write a `create-topics.sh`, set retention, set compaction policy, provision topics for Confluent Cloud, or generate idempotent topic scripts.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%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 body is appropriately lean and organized, but its guidance is incomplete: the command template uses placeholders, lacks a full executable script, and omits the verification/idempotency steps that a batch provisioning workflow demands.

Suggestions

Replace the 'retention.ms=...' and 'cleanup.policy=...' placeholders with concrete example values and show the full create-topics.sh script (shebang, loop over topics, the confluent create call).

Add a verification/idempotency checkpoint — e.g., check whether a topic already exists before creating it, or run 'confluent kafka topic describe' afterward to confirm the applied config.

Demonstrate the idempotent topic-script generation promised in the description, since the body currently never shows how idempotency is achieved.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — 'Generate create-topics.sh with retention/compaction settings' and a single command template — with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	It gives a real command ('confluent kafka topic create --config retention.ms=... --config cleanup.policy=...') but uses '...' placeholders rather than executable values, shows no full script structure (shebang, loop, error handling), and never demonstrates the idempotency the description promises.	3 / 5
Workflow Clarity	Two steps are sequenced (ask for parameters, then generate), but topic provisioning is a batch operation with no validation or verification checkpoint (e.g., confirm a topic exists before creating it for idempotency), which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	At well under 50 lines with no external references needed, the content is organized into clearly labeled sections (Step 1, Step 2), satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	16 / 20 Passed

Description

100%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.

A well-crafted description that concretely states capabilities and provides explicit, natural trigger guidance with strong keyword coverage. It cleanly answers both what the skill does and when to use it within a distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Build a Confluent Cloud topic provisioning script with retention and compaction', set retention, set compaction policy, provision topics, generate idempotent scripts — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ('Build a Confluent Cloud topic provisioning script with retention and compaction') and when ('Use when the user asks to create a topic...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when...' clause covers natural phrases users would say ('create a topic', 'set retention', 'set compaction policy', 'provision topics for Confluent Cloud') plus the concrete script filename 'create-topics.sh', giving comprehensive keyword coverage including synonyms.	5 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Confluent Cloud topic provisioning — with distinct, domain-specific triggers, so overlap risk with other skills is minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: skills/confluent-skill-reviewer/evals/mock-skills/trigger-overlap/SKILL.md
Commit: db79f9e

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.