airflow-dag-generator
Airflow Dag Generator - Auto-activating skill for Data Pipelines. Triggers on: airflow dag generator, airflow dag generator Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill airflow-dag-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The redundant trigger terms and boilerplate category mention provide no value for skill selection.
Suggestions
Add specific concrete actions like 'Generates Apache Airflow DAG Python files, configures task dependencies, sets scheduling intervals, and defines operators for data pipeline workflows'.
Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions Airflow, DAG files, data pipelines, workflow scheduling, ETL automation, or needs to create Python DAG definitions'.
Remove the redundant trigger term and expand to include variations users would naturally say: 'airflow', 'DAG', 'data pipeline', 'workflow', 'ETL', 'scheduled tasks', 'pipeline orchestration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Airflow Dag Generator') without describing any concrete actions. There are no specific capabilities listed like 'creates DAG files', 'configures task dependencies', or 'sets scheduling parameters'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a repetition of the skill name rather than explicit trigger scenarios. There is no 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('airflow dag generator' listed twice) and miss natural variations users would say like 'create airflow pipeline', 'DAG file', 'workflow automation', 'data pipeline', or 'schedule tasks'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Airflow' is a specific technology that provides some distinctiveness, the generic 'Data Pipelines' category and lack of specific triggers could cause overlap with other pipeline or workflow skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what an Airflow DAG generator skill might do but provides absolutely no actionable guidance, code examples, DAG templates, or workflow instructions. The entire content could be replaced with a single sentence without losing information.
Suggestions
Add concrete, executable DAG code examples showing common patterns (e.g., ETL pipeline, sensor-based triggers, task dependencies)
Include a step-by-step workflow for creating a DAG: define tasks → set dependencies → configure schedule → validate → deploy
Provide specific Airflow operator examples (PythonOperator, BashOperator, sensors) with copy-paste ready code
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical content
| 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 DAG templates, no specific Airflow operators or patterns. The skill describes what it could do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating a DAG, no validation checkpoints, and no sequence of operations. The content is entirely abstract with no process guidance. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, templates, or advanced documentation. It provides no path to deeper information. | 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
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.