Flink Job Creator - Auto-activating skill for Data Pipelines. Triggers on: flink job creator, flink job creator Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill flink-job-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or usage guidance. Claude would struggle to know when to select this skill or what capabilities it provides.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Apache Flink streaming jobs, configures source/sink connectors, defines data transformations and windowing operations'
Include a 'Use when...' clause with natural trigger terms like 'Use when building streaming pipelines, real-time data processing, Flink SQL queries, or Apache Flink job configuration'
Add common user phrases and file types: 'streaming jobs', 'real-time analytics', 'Kafka integration', 'event processing', '.sql files for Flink'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Flink Job Creator') and category ('Data Pipelines') without describing any concrete actions. There are no specific capabilities listed like 'create streaming jobs', 'configure connectors', or 'define 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 only trigger terms listed are 'flink job creator' repeated twice, which is redundant and overly specific. Missing natural variations users might say like 'streaming pipeline', 'Flink SQL', 'data stream', 'Apache Flink', or 'real-time processing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flink' provides some specificity that distinguishes it from generic data processing skills, but 'Data Pipelines' is broad and could overlap with other ETL or streaming tools. The lack of specific Flink capabilities makes differentiation weak. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content about Flink job creation. It consists entirely of generic boilerplate that could apply to any skill, providing zero actionable guidance, code examples, or specific information about Apache Flink or data pipeline creation.
Suggestions
Add executable Flink job code examples (e.g., a basic DataStream job in Java/Scala/Python with source, transformation, and sink)
Include specific Flink configuration parameters and deployment commands (e.g., `flink run -c MainClass job.jar`)
Define a clear workflow: 1) Set up environment, 2) Define sources/sinks, 3) Implement transformations, 4) Test locally, 5) Deploy to cluster
Reference detailed documentation for advanced topics like checkpointing, state management, and windowing operations
| 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 Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually create a Flink job. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. Claims to provide 'step-by-step guidance' but includes zero actual steps for creating Flink jobs. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no structure for discovery or deeper learning. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.