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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill luigi-task-generatorOverall
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 only distinguishing element is the mention of 'Luigi' as a specific framework, but without describing what the skill does with Luigi, Claude cannot make informed decisions about when to select it.
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'
Include a 'Use when...' clause with natural trigger terms like 'luigi pipeline', 'batch data workflow', 'ETL task', 'data dependency graph', 'Python pipeline orchestration'
Expand trigger terms to include variations users might naturally say: 'luigi', 'data pipeline', 'task dependencies', 'workflow automation', 'batch processing'
| 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 the 'when' clause is essentially just the skill name repeated. There's no explicit guidance on when Claude should select this skill or what user requests would trigger it. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'luigi task generator' repeated twice. This misses natural variations users might say like 'create luigi pipeline', 'luigi workflow', 'data pipeline task', 'ETL task', or 'batch processing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Luigi' (a specific Python framework) provides some distinctiveness from generic data pipeline skills. However, 'Data Pipelines' is broad and could overlap with other ETL or workflow skills. The lack of specific capabilities makes differentiation difficult. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no substantive information. It describes what a Luigi task generator skill would do without providing any actual guidance, code examples, or workflows. Claude would gain nothing actionable from this content that it doesn't already know.
Suggestions
Add executable Python code examples showing how to create Luigi Task classes with requires(), output(), and run() methods
Include a concrete workflow for generating Luigi tasks: define dependencies, specify outputs, implement run logic, validate task graph
Remove all generic boilerplate ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual Luigi-specific patterns and anti-patterns
Add references to Luigi documentation or example files for advanced topics like task parameters, dynamic dependencies, and central scheduler configuration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about Luigi task generation. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty filler that waste tokens without teaching anything. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no actual instructions for generating Luigi tasks. The content only describes what the skill claims to do rather than providing executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill mentions 'step-by-step guidance' but provides none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no structure for learning. There are no references to detailed documentation, examples, or related files that would help Claude actually perform Luigi task generation. | 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.