building-cicd-pipelines
Execute use when you need to work with deployment and CI/CD. This skill provides deployment automation and pipeline orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
45
33%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/ci-cd-pipeline-builder/skills/building-cicd-pipelines/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description relies heavily on vague buzzwords ('comprehensive guidance and automation', 'pipeline orchestration') without specifying concrete actions the skill performs. While it includes some trigger phrases, the lack of specific capabilities makes it hard to distinguish from other DevOps-related skills and provides little information for Claude to make an informed selection.
Suggestions
Replace vague language with specific concrete actions, e.g., 'Generates CI/CD pipeline configurations (GitHub Actions, GitLab CI, Jenkins), creates Dockerfiles, configures deployment scripts, and sets up automated testing stages.'
Expand trigger terms to include common variations like 'CI/CD', 'GitHub Actions', 'Jenkins', 'release pipeline', 'build automation', 'continuous integration', 'continuous deployment'.
Clarify the scope boundaries to reduce conflict risk, e.g., specify which platforms or tools are covered and what distinguishes this from general infrastructure or container skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, buzzword-heavy language like 'deployment automation and pipeline orchestration with comprehensive guidance and automation.' No concrete actions are listed—it doesn't specify what it actually does (e.g., configure YAML pipelines, push to Docker registries, run tests). | 1 / 3 |
Completeness | It has a 'Use when' clause and trigger phrases, addressing the 'when' aspect. However, the 'what' is extremely vague—'deployment automation and pipeline orchestration with comprehensive guidance' doesn't concretely explain what the skill does, so the 'what' is very weak. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger phrases like 'deploy application', 'create pipeline', and 'automate deployment', which are natural terms users might say. However, it misses common variations like 'CI/CD', 'GitHub Actions', 'Jenkins', 'release', 'build pipeline', '.yml', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The terms 'deployment' and 'CI/CD' provide some domain specificity, but the description is broad enough that it could overlap with infrastructure-as-code skills, Docker skills, cloud platform skills, or general DevOps skills without clear boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level overview or checklist for CI/CD pipeline creation rather than actionable guidance. Its most critical weakness is the complete absence of executable code examples—no YAML snippets, no Jenkinsfile fragments, no actual pipeline configurations—which is especially problematic for a skill whose entire purpose is generating these artifacts. The error handling table is a useful addition, but the skill would benefit enormously from concrete, platform-specific templates and a proper bundle structure.
Suggestions
Add concrete, executable pipeline configuration examples for at least 2-3 platforms (e.g., a complete GitHub Actions YAML workflow and a GitLab CI YAML) that Claude can use as templates.
Create separate bundle files for each platform (e.g., `github-actions.md`, `gitlab-ci.md`, `jenkins.md`) with platform-specific templates, syntax details, and examples, then reference them from the main SKILL.md.
Add explicit validation feedback loops: after generating a pipeline config, validate syntax with the platform tool, check for common errors, and iterate until valid.
Remove the Prerequisites and Resources sections (Claude already knows these) and replace with the saved space for actual code templates and patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the Prerequisites section (Claude knows what Docker and Git are), the Resources section with well-known URLs, and the Examples section which describes prompts rather than providing executable examples. The error handling table adds value but is somewhat verbose. | 2 / 3 |
Actionability | Despite being about generating CI/CD pipeline configurations, the skill contains zero executable code examples, no concrete YAML snippets, no actual pipeline templates, and no copy-paste ready configurations. The instructions are high-level descriptions of what to do rather than concrete guidance on how to do it. | 1 / 3 |
Workflow Clarity | The 10-step instruction sequence provides a clear ordering of stages, and step 10 mentions syntax validation. However, there are no explicit feedback loops (validate -> fix -> retry), no checkpoints between steps, and no guidance on what to do when validation fails. For a skill involving generating complex configuration files, the lack of verification steps is notable. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic document with no bundle files and no references to supporting files. All content—prerequisites, instructions, error handling, examples, resources—is inline. For a skill covering 5 different CI/CD platforms, there should be platform-specific reference files rather than trying to cover everything in one document while actually covering nothing in depth. | 1 / 3 |
Total | 6 / 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
3a2d27d
- 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.