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
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 is a very weak description that essentially only provides the skill name and category with no substantive content. It lacks concrete actions, meaningful trigger terms, and any 'when to use' guidance. The trigger terms are the skill name duplicated, providing no additional discoverability.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Dagster assets, defines jobs, configures IO managers, sets up schedules and sensors for data pipeline orchestration.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about building data pipelines with Dagster, creating Dagster assets, defining ETL workflows, or setting up orchestration with Dagster.'
Include natural keyword variations users might say, such as 'dagster', 'data pipeline', 'ETL', 'orchestration', 'dagster assets', 'dagster jobs', 'data engineering'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions beyond the name 'Dagster Pipeline Creator'. It does not list specific capabilities like defining assets, scheduling jobs, configuring resources, or any other concrete actions. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague implication of creating Dagster pipelines, and it has no explicit 'when to use' guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger context. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('dagster pipeline creator, dagster pipeline creator'). It misses natural user terms like 'dagster', 'data pipeline', 'ETL', 'orchestration', 'assets', 'jobs', 'schedules', or 'dagster project'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Dagster' provides some specificity that distinguishes it from generic pipeline tools, but 'Data Pipelines' category overlap and lack of detail about what specifically this does with Dagster (vs other Dagster-related skills) limits distinctiveness. | 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 substantive content. It contains only meta-descriptions of what the skill would do without any actual Dagster-specific instructions, code examples, pipeline definitions, or workflows. It provides no value beyond what Claude already knows about Dagster.
Suggestions
Add concrete, executable Dagster code examples showing asset definitions, jobs, resources, and IO managers for common pipeline patterns (e.g., ETL from a database to a data warehouse).
Define a clear multi-step workflow for creating a Dagster pipeline: project scaffolding (`dagster project scaffold`), defining assets, configuring resources, testing locally (`dagster dev`), and deploying.
Include Dagster-specific best practices such as partitioning strategies, software-defined assets vs ops/graphs, sensor/schedule configuration, and error handling patterns.
Remove all the meta-content (Purpose, When to Use, Example Triggers, Capabilities) and replace with actionable technical content that Claude doesn't already know.
| 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. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no commands, no Dagster-specific configurations, no pipeline definitions, no asset definitions—nothing Claude could actually use to create a Dagster pipeline. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. There is no sequence of actions, no validation checkpoints, and no process for creating a Dagster pipeline. The content only describes trigger phrases and vague capabilities. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-information with no references to supporting files, no structured navigation, and no separation of overview from detailed content. There are no bundle files to support it either. | 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
172d892
- 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.