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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill dagster-pipeline-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The only distinguishing element is the 'Dagster' keyword.
Suggestions
Add specific concrete actions like 'Creates Dagster assets, jobs, schedules, and resources. Generates software-defined assets with proper dependencies and IO managers.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions Dagster, data pipelines, ETL workflows, orchestration, asset definitions, or needs to create data engineering infrastructure.'
Include common file types or concepts: '.py pipeline files, @asset decorators, Definitions objects, dagster.yaml configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Dagster Pipeline Creator' and 'Auto-activating skill for Data Pipelines' without describing any concrete actions. No specific capabilities like 'create assets', 'define jobs', or 'configure schedules' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or explicit trigger guidance. Both the what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'dagster pipeline creator' repeated twice. Missing natural variations users would say like 'data pipeline', 'ETL', 'orchestration', 'dagster assets', 'dagster jobs', or 'workflow automation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Dagster' provides some specificity that distinguishes it 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%This skill content is essentially a placeholder template with no actual Dagster-specific information. It contains only generic boilerplate about what the skill claims to do without providing any concrete guidance, code examples, or actionable instructions for creating Dagster pipelines. The content fails on all dimensions because it teaches nothing.
Suggestions
Add executable Python code examples showing how to create a basic Dagster asset and job (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 CLI commands (e.g., 'dagster dev', 'dagster job execute') with example usage
Reference Dagster-specific concepts like assets, ops, jobs, resources, and IO managers with brief, actionable explanations of when to use each
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about Dagster. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific Dagster concepts, no actual instructions for creating pipelines. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for pipeline creation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to detailed materials, no links to examples, API references, or advanced topics. There's nothing to disclose progressively because there's no substantive content. | 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.