beam-pipeline-builder
Beam Pipeline Builder - Auto-activating skill for Data Pipelines. Triggers on: beam pipeline builder, beam pipeline builder Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill beam-pipeline-builderOverall
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 providing any meaningful information about capabilities or usage triggers. It relies entirely on the user knowing exactly what 'Beam Pipeline Builder' means and fails to help Claude distinguish when to use this skill versus other data processing skills.
Suggestions
Add specific concrete actions like 'Creates Apache Beam pipelines, defines PTransforms, configures runners (Dataflow, Flink, Spark), handles PCollections and windowing operations'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions Apache Beam, Dataflow pipelines, batch/streaming data processing, or building ETL workflows'
Include common file extensions or artifacts: '.py beam pipelines', 'pipeline options', 'DoFn classes', 'beam.yaml configurations'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'Beam Pipeline Builder' and 'Data Pipelines' without describing any concrete actions. There are no specific capabilities listed like 'create transforms', 'configure runners', or 'define PCollections'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no 'Use when...' clause or explicit guidance on when Claude should select this skill. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'beam pipeline builder' repeated twice, which is redundant and overly specific. Missing natural variations users might say like 'Apache Beam', 'dataflow', 'batch processing', 'streaming pipeline', or 'ETL'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Beam Pipeline Builder' is somewhat specific to Apache Beam, the generic 'Data Pipelines' category could overlap with other ETL or data processing skills. The lack of specific capabilities makes it harder to distinguish from similar tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content about Apache Beam pipeline development. It contains only generic boilerplate text that could apply to any skill, with no executable code, specific patterns, or actionable guidance for building data pipelines with Beam.
Suggestions
Add executable Python code examples showing basic Beam pipeline construction (e.g., ReadFromText -> transforms -> WriteToText)
Include specific Beam concepts like PCollections, ParDo, GroupByKey with concrete usage examples
Define a clear workflow for pipeline development: create -> test locally -> validate -> deploy with specific commands
Reference external documentation for advanced topics (windowing, triggers, runners) with clear one-level-deep links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Beam pipelines. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually build a Beam pipeline. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There's no sequence for building a Beam pipeline, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed documentation, examples, or related files. No structure for discovery or navigation. | 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.