This is an excellent skill description that excels across all dimensions. It provides comprehensive coverage of specific capabilities, uses natural domain terminology, includes explicit 'Use when' triggers with numbered scenarios, and carves out a distinct niche in the Flink/Confluent ecosystem. The description is well-structured, uses proper third-person voice, and balances technical depth with clarity.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: writing Flink SQL queries, building Table API pipelines, creating UDFs, deploying to Confluent Cloud, converting between APIs, and troubleshooting. Also specifies technical domains like windows, joins, aggregations, MATCH_RECOGNIZE, watermarks, and state management.	3 / 3
Completeness	Clearly answers both what (Apache Flink SQL, Table API, UDF development) and when with explicit numbered triggers using 'Use when:' clause covering six specific scenarios. The explicit trigger guidance is comprehensive and well-structured.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Flink SQL', 'Table API', 'UDF', 'Confluent Cloud', 'DataStream', 'windowing', 'watermarks', 'event-time processing'. Includes both OSS Flink and Confluent-specific terminology that users in this domain would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with clear niche targeting Apache Flink specifically, distinguishing between OSS Flink and Confluent Cloud. The specific technologies (Flink SQL, Table API, MATCH_RECOGNIZE, DataStream) create a unique fingerprint unlikely to conflict with general SQL or streaming skills.	3 / 3
	Total	12 / 12 Passed

Implementation

87%

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

This is a high-quality skill with excellent token efficiency, actionable code examples, and well-organized progressive disclosure. The main weakness is the lack of explicit validation checkpoints in multi-step workflows like UDF deployment, though the troubleshooting table partially compensates. The mental model section effectively conveys the core streaming concept without over-explaining.

Suggestions

Add explicit validation steps to the UDF deployment workflow (e.g., 'Verify artifact upload: confluent flink artifact list', 'Test function: SELECT my_upper('test')')

Dimension	Reasoning	Score
Conciseness	Extremely efficient use of tokens. Uses tables for quick reference, minimal prose, and assumes Claude understands SQL and streaming concepts. No unnecessary explanations of what Flink or SQL is.	3 / 3
Actionability	Provides fully executable code examples throughout - SQL queries, Java/Python setup, UDF examples, CLI commands for deployment. All examples are copy-paste ready with complete syntax.	3 / 3
Workflow Clarity	While individual patterns are clear, the UDF deployment workflow lacks explicit validation steps. The 'Critical Rules' section mentions important constraints but doesn't integrate them into step-by-step workflows with checkpoints.	2 / 3
Progressive Disclosure	Excellent structure with a concise overview and clear one-level-deep references to detailed guides (udf-guide.md, troubleshooting.md, etc.). Reference files are well-signaled with descriptive labels.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Install with Tessl CLI

npx tessl i gamussa/flink-sql

Reviewed

3 days ago

Table of Contents

Discovery Implementation Validation