CtrlK
BlogDocsLog inGet started
Tessl Logo

confluent-cloud-flink-sql

Write and debug Flink SQL that runs on Confluent Cloud, enforcing the CC-vs-Apache-Flink (OSS) dialect boundary. Use when the working directory is a Confluent Cloud Flink workspace, when a Flink SQL statement needs checking before it runs on a CC compute pool, or when the user mentions CC Flink, Confluent Cloud Flink SQL, the `confluent flink` CLI, a CFU compute pool, `CREATE CONNECTION`, or asks to check or debug Flink SQL whose runtime is Confluent Cloud. Also trigger when a Flink SQL question is posed and nothing establishes an Apache Flink OSS runtime. Do NOT trigger for: building or deploying Flink UDFs in Java (UDF/UDTF/PTF — use flink-udf); a full CDC pipeline from a database through Flink into Tableflow/Iceberg/Delta Lake (use confluent-cloud-cdc-tableflow); Kafka Streams topology work (use kafka-streams-programming); or Flink SQL confirmed to run on Apache Flink OSS, not Confluent Cloud.

74

Quality

93%

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

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

A well-engineered skill body: lean, highly actionable, with a verification loop that embeds validation checkpoints and escalation paths, and a clean progressive-disclosure structure backed by real reference files. Conciseness is the only dimension with minor room to tighten (scope note / hierarchy sections).

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence (no "what is Flink" padding), with every section earning its place; the scope note and source-of-truth hierarchy add modest length that could be trimmed slightly but is justified.

4 / 5

Actionability

Provides concrete, copy-paste-ready CLI commands (statement create with --wait, kafka topic consume with format mapping) and exact escalation commands covering the common cases, with intentional <placeholder> tokens for unverified identifiers.

5 / 5

Workflow Clarity

The verification loop is a numbered 0-5 sequence with explicit validation checkpoints (EXPLAIN before create, wait for user confirmation), escalation-required states, and loud-failure feedback for statement exceptions — covering the destructive/batch cap.

5 / 5

Progressive Disclosure

Clean overview with a one-level-deep Reference files table mapping each file to its load condition; all six referenced files exist and bulk content is appropriately split out rather than inlined.

5 / 5

Total

19

/

20

Passed

Description

90%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 strong, highly-specific description with explicit trigger phrases, a clear what/when structure, and effective negative boundaries that distinguish it from neighboring skills. The only mild weakness is that the stated actions (write, debug) under-represent the full range of concrete behaviors the skill supports.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Write and debug Flink SQL"), but does not enumerate further actions like EXPLAIN, verification, or trap-checking that the skill actually performs, so coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both what ("Write and debug Flink SQL that runs on Confluent Cloud, enforcing the dialect boundary") and when with concrete "Use when..." / "Also trigger when..." phrases, plus negative "Do NOT trigger for" guidance.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms ("CC Flink", "Confluent Cloud Flink SQL"), the concrete CLI ("confluent flink"), and resource markers ("CFU compute pool", "CREATE CONNECTION").

5 / 5

Distinctiveness Conflict Risk

Negative triggers explicitly disambiguate from flink-udf, confluent-cloud-cdc-tableflow, kafka-streams-programming, and OSS Flink, establishing a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.