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
Quality
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 severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs, relies on redundant trigger terms, and lacks any guidance for when Claude should select this skill. The only redeeming quality is the specific mention of 'Luigi' which provides minimal distinctiveness.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Luigi task classes, defines task dependencies, creates pipeline configurations, and sets up data workflow DAGs'
Add a 'Use when...' clause with natural trigger terms like 'Use when building Python data pipelines, creating Luigi tasks, defining workflow dependencies, or setting up batch processing jobs'
Expand trigger terms to include variations users would naturally say: 'luigi pipeline', 'python workflow', 'task dependencies', 'batch data processing', 'ETL pipeline'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Luigi Task Generator', 'Data Pipelines') but provides no concrete actions. There's no indication of what the skill actually does - no verbs describing capabilities like 'generates', 'creates', 'configures', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause or equivalent guidance. The 'Triggers on' section is not a proper 'when' explanation - it just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('luigi task generator' listed twice) and overly specific. Missing natural variations users might say like 'luigi pipeline', 'create luigi task', 'data pipeline task', or 'workflow automation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Luigi' (a specific Python framework) provides some distinctiveness from generic data pipeline skills, but 'Data Pipelines' category is broad and could overlap with other ETL or workflow tools like Airflow, Prefect, or dbt. | 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 content is entirely generic boilerplate with no actionable information about Luigi task generation. It lacks any concrete code examples, specific commands, workflow steps, or references to detailed documentation. The content could apply to virtually any topic by swapping out the phrase 'luigi task generator.'
Suggestions
Add a concrete, executable Python code example showing how to create a basic Luigi task with Target and requires() method
Include a clear workflow sequence: define task -> specify dependencies -> set output targets -> run with luigi command
Remove generic capability descriptions and replace with specific Luigi patterns (e.g., LocalTarget vs S3Target, task parameters, dependency graphs)
Add references to detailed documentation for advanced topics like task scheduling, failure handling, and central scheduler configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Luigi task generation. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('Generates production-ready code') but never shows how to actually create a Luigi task. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There's no sequence for creating Luigi tasks, no validation checkpoints, and no actual process to follow—just vague capability claims. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials, no references to examples or API documentation, and no clear navigation to learn more. | 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.