dagster-pipeline-creator
Dagster Pipeline Creator - Auto-activating skill for Data Pipelines. Triggers on: dagster pipeline creator, dagster pipeline creator Part of the Data Pipelines skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.03xAverage 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/dagster-pipeline-creator/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, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others, and the redundant trigger terms suggest auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Dagster assets, jobs, schedules, and resource configurations for data orchestration workflows'
Add a 'Use when...' clause with natural trigger terms like 'dagster', 'data pipeline', 'ETL workflow', 'orchestration', 'asset materialization', or 'scheduled data jobs'
Include file types or contexts that would trigger this skill, such as 'when working with Python data engineering projects' or 'when user mentions dagster.yaml or assets.py'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Dagster Pipeline Creator' and 'Data Pipelines' without describing any concrete actions. It doesn't explain what creating a pipeline involves (e.g., defining assets, scheduling jobs, configuring resources). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'dagster pipeline creator' repeated twice - no natural variations users might say like 'create dagster job', 'data pipeline', 'ETL', 'orchestration', or 'dagster assets'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Dagster' specifically provides some distinctiveness from generic pipeline tools, but 'Data Pipelines' is vague enough to potentially conflict with other ETL or orchestration skills. | 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 with no actual instructional content. It describes what a Dagster pipeline creator skill would do without providing any concrete guidance, code examples, or actionable steps. The entire content is meta-description that wastes tokens explaining the skill's existence rather than teaching Claude how to create Dagster pipelines.
Suggestions
Add executable Python code examples showing basic Dagster asset and job definitions (e.g., @asset decorator, Definitions object)
Include a concrete workflow for creating a pipeline: define assets → configure resources → create job → test locally → deploy
Provide specific Dagster patterns like asset dependencies, partitions, and IO managers with copy-paste ready code
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers') 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 step-by-step guidance' and 'Follows industry best practices' are meaningless filler without actual content. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual Dagster pipeline creation. The entire skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for creating Dagster pipelines. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual resources, examples, or detailed materials. No references to additional documentation or organized sections for different aspects of Dagster pipeline creation. | 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.