flink-job-creator
Flink Job Creator - Auto-activating skill for Data Pipelines. Triggers on: flink job creator, flink job creator Part of the Data Pipelines skill category.
34
3%
Does it follow best practices?
Impact
87%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/flink-job-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely minimal and essentially just restates the skill name and category without providing any useful information about capabilities or selection criteria. It lacks concrete actions, natural trigger terms, and explicit 'use when' guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Apache Flink streaming and batch jobs, defines source/sink connectors, writes Flink SQL queries, and configures job deployment settings.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating Flink jobs, building streaming pipelines, writing Flink SQL, configuring Kafka connectors, or deploying data processing applications.'
Remove the redundant duplicate trigger term and replace with diverse natural keywords users would actually say, such as 'stream processing', 'Flink application', 'real-time data pipeline', 'Flink SQL', 'Apache Flink'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only names itself ('Flink Job Creator') and its category ('Data Pipelines') without describing what it actually does—no mention of creating jobs, configuring pipelines, writing SQL, defining sources/sinks, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a self-referential trigger ('flink job creator') with no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'flink job creator' repeated twice. There are no natural user keywords like 'Flink SQL', 'streaming job', 'data pipeline', 'Kafka source', 'Flink application', or other terms a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flink' provides some domain specificity that distinguishes it from generic data pipeline skills, but the lack of concrete actions or detailed triggers means it could still overlap with other Flink-related or data pipeline skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content about creating Flink jobs. It contains only generic boilerplate sections that describe what the skill would do without providing any actionable information, code examples, configuration templates, or workflow guidance. It adds zero value beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable Flink job code examples (e.g., a minimal Java/Python Flink job with source, transformation, and sink operators) that are copy-paste ready.
Define a clear multi-step workflow for creating a Flink job: project setup, job definition, local testing, deployment to a cluster, and validation/monitoring steps with explicit checkpoints.
Include specific configuration examples (e.g., flink-conf.yaml settings, parallelism configuration, checkpointing setup) and common patterns for streaming vs. batch jobs.
Remove all generic boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that provide no actionable information and replace with domain-specific content about Flink job patterns, common pitfalls, and best practices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'flink job creator' excessively, and contains zero substantive information about actually creating Flink jobs. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no configuration examples, no API references. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps, no sequencing, and no validation checkpoints for creating Flink jobs. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to examples or configuration files, and no meaningful structural organization. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.