Airflow Operator Creator - Auto-activating skill for Data Pipelines. Triggers on: airflow operator creator, airflow operator creator Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill airflow-operator-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 guidance on when to use the skill. The repeated trigger term and generic category mention provide almost no value for skill selection.
Suggestions
Add specific capabilities: 'Creates custom Airflow operators, generates operator boilerplate, implements sensors and hooks, configures task parameters'
Include a 'Use when...' clause with natural triggers: 'Use when the user needs to create custom Airflow operators, build DAG tasks, implement sensors, or extend Airflow functionality'
Add natural keyword variations users would say: 'custom operator', 'DAG task', 'PythonOperator', 'BashOperator', 'sensor', 'hook', 'airflow plugin'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Airflow Operator Creator') without describing any concrete actions. There are no specific capabilities listed like 'creates custom operators', 'generates boilerplate code', or 'configures task dependencies'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the category ('Data Pipelines') without explaining capabilities or providing explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('airflow operator creator, airflow operator creator'). Missing natural user phrases like 'create airflow operator', 'custom operator', 'DAG task', 'python operator', or 'sensor'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Airflow Operator' is somewhat specific to Apache Airflow, the lack of detail means it could conflict with other Airflow-related skills or general data pipeline skills. The category mention provides some distinction but is insufficient. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It describes what the skill claims to do without providing any concrete guidance, code examples, or workflows for creating Airflow operators. The content would need to be completely rewritten with actual operator creation patterns, executable code, and clear workflows.
Suggestions
Add executable Python code examples showing how to create custom Airflow operators (e.g., BaseOperator subclass with execute method)
Include a clear workflow: 1) Define operator class, 2) Implement execute(), 3) Register in plugin, 4) Test with DAG - with validation steps
Provide concrete examples of common operator patterns (sensor operators, transfer operators, hook-based operators) with copy-paste ready code
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions for creating Airflow operators. The entire content describes what the skill does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for creating Airflow operators. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. There are no references to detailed documentation, examples, or related files - just empty category tags. | 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.