luigi-task-generator
Luigi Task Generator - Auto-activating skill for Data Pipelines. Triggers on: luigi task generator, luigi task generator Part of the Data Pipelines skill category.
36
3%
Does it follow best practices?
Impact
100%
3.33xAverage 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/luigi-task-generator/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 essentially a template placeholder with no substantive content. It names the technology (Luigi) but fails to describe any concrete actions, lacks meaningful trigger terms, and provides no guidance on when Claude should select this skill. The repeated trigger term adds no value.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Luigi Task classes with proper dependencies, parameters, output targets, and run methods for building Python data pipelines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Luigi tasks, Luigi pipelines, Luigi workflows, ETL pipelines in Python, or mentions luigi.Task, luigi.Target, or data pipeline dependencies.'
Include keyword variations users might naturally say, such as 'luigi', 'luigi pipeline', 'luigi workflow', 'luigi dependency graph', 'ETL task', 'data pipeline Python', '.py pipeline'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Luigi Task Generator' and 'Data Pipelines' but provides no concrete actions. There is no mention of what the skill actually does—no verbs describing specific capabilities like generating task classes, defining dependencies, or creating pipeline configurations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially just restating the skill name as a trigger. There is no explicit 'Use when...' guidance with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'luigi task generator' repeated twice. There are no natural keyword variations a user might say, such as 'luigi pipeline', 'luigi workflow', 'luigi dependency', 'data pipeline task', or 'ETL pipeline'. The terms are narrow and redundant. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Luigi' (a specific Python framework) provides some distinctiveness from generic data pipeline skills. However, the vague 'Data Pipelines' category label could overlap with other pipeline-related skills like Airflow or Prefect generators. | 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 or template with no substantive content. It contains no actual instructions, code, or technical guidance for generating Luigi tasks. Every section describes the skill's purpose in abstract terms rather than providing actionable information Claude could use.
Suggestions
Add concrete, executable Python code showing how to define a Luigi Task class with requires(), output(), and run() methods, including a complete working example.
Include a clear multi-step workflow for generating Luigi tasks: e.g., 1) Define dependencies, 2) Implement output targets, 3) Write run logic, 4) Validate the task graph with `luigi --dry-run`.
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace them with actual technical content — patterns for common Luigi task types (ExternalTask, WrapperTask, etc.) with copy-paste ready code.
Add at least one complete end-to-end example showing a small Luigi pipeline (e.g., extract → transform → load) with specific file paths, parameter definitions, and validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding that convey no useful information to Claude. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no Luigi task definitions, no commands, no configuration snippets. The entire skill describes rather than instructs — it never actually shows how to generate a Luigi task. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. There is no sequence of actions, no validation checkpoints, and no error handling guidance. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure that aids navigation. There are no references to supporting files, no separation of quick-start vs. advanced content, and no bundle files to support it. | 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
ba8561d
- 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.