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
Quality
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 severely underdeveloped, essentially only providing a skill name and category without any substantive content. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The redundant trigger terms and absence of capability details make it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions like 'Creates Apache Flink streaming jobs, configures source/sink connectors, defines data transformations and windowing operations'
Add a 'Use when...' clause with natural trigger terms: 'Use when building streaming pipelines, real-time data processing, Flink SQL queries, Kafka integration, or event-driven architectures'
Include file type or technology triggers users would mention: 'flink sql', 'streaming job', 'kafka connector', 'data stream', '.sql files for Flink'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Flink Job Creator' and 'Auto-activating skill for Data Pipelines' without describing any concrete actions. There are no specific capabilities listed like 'creates streaming jobs', 'configures connectors', or 'defines data transformations'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no explicit 'when to use' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The triggers listed are redundant ('flink job creator, flink job creator') and only cover the exact skill name. Missing natural variations users would say like 'streaming pipeline', 'kafka connector', 'flink sql', 'data stream', or 'real-time processing'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Flink' is a specific technology that provides some distinctiveness, the generic 'Data Pipelines' category and lack of specific Flink capabilities could cause overlap with other data processing or 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 essentially a placeholder template with no actual content about Flink job creation. It describes what a skill should do in abstract terms but provides zero actionable guidance, code examples, or specific instructions. The entire content could be replaced with actual Flink job creation patterns and would be far more useful.
Suggestions
Add executable Flink job code examples showing common patterns (e.g., DataStream API usage, source/sink configuration, windowing operations)
Include a concrete workflow for creating a Flink job: project setup, job definition, local testing, deployment steps with validation checkpoints
Replace generic capability claims with specific Flink concepts: state management, checkpointing configuration, exactly-once semantics setup
Add references to detailed files for advanced topics like Flink SQL, Table API, or production deployment configurations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Flink job creation. Phrases like 'automated assistance' and 'industry best practices' are filler that waste tokens without providing actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it claims to do but never actually shows how to create a Flink job - no code examples, no configuration snippets, no specific steps. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. Despite claiming to provide 'step-by-step guidance,' the skill contains zero actual steps for creating a Flink job. No sequence, no validation, no checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual implementation details. No references to detailed documentation, examples, or related files that would contain the real content. | 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
0c08951
- 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.