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".
36
33%
Does it follow best practices?
Impact
—
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.
This description relies heavily on abstract buzzwords ('comprehensive guidance and automation', 'pipeline orchestration') without specifying concrete actions the skill performs. While it includes some useful trigger phrases, the lack of specific capabilities makes it difficult to distinguish from other DevOps-related skills and provides little confidence about what the skill actually does.
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 for cloud providers (AWS, GCP, Azure).'
Expand trigger terms to include common variations users would say: 'CI/CD', 'GitHub Actions', 'Jenkins pipeline', 'release process', 'continuous integration', 'continuous deployment', 'build and deploy'.
Strengthen the 'what' portion by listing 3-5 specific tasks the skill handles rather than using abstract nouns like 'orchestration' and 'automation'.
| 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 in CI). | 1 / 3 |
Completeness | It has a weak 'what' (deployment automation and pipeline orchestration) and does include trigger phrases serving as a 'when' clause. However, the 'what' is so vague that the completeness is undermined—it technically addresses both but neither with sufficient depth. | 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 many common variations like 'CI/CD', 'GitHub Actions', 'Jenkins', 'release', 'build pipeline', 'continuous integration', or specific tool names. | 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 provider 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 Claude can execute. Its biggest weakness is the complete absence of concrete code examples—no YAML snippets, no Jenkinsfile fragments, no Dockerfile templates—despite the skill's purpose being to generate these artifacts. The error handling table is a useful addition, but the skill would benefit enormously from executable templates and better content organization across multiple files.
Suggestions
Add concrete, executable pipeline configuration examples: at minimum a GitHub Actions YAML workflow, a GitLab CI YAML, and a Jenkinsfile snippet that Claude can use as templates and adapt.
Split platform-specific templates into separate referenced files (e.g., `github-actions-template.yml`, `gitlab-ci-template.yml`) and reference them from the main SKILL.md to improve progressive disclosure.
Add explicit validation checkpoints with feedback loops, e.g., 'After generating the workflow file, validate with `actionlint .github/workflows/ci.yml`. If errors, fix and re-validate before committing.'
Remove the Prerequisites and Resources sections (Claude already knows these platforms and URLs) and replace with space for actual code templates.
| 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 output. The error handling table adds value but the overall content could be tightened significantly. | 2 / 3 |
Actionability | Despite being about generating pipeline configurations, the skill contains zero executable code examples, no actual YAML snippets, no Jenkinsfile fragments, and no concrete pipeline templates. The instructions are a high-level checklist of abstract steps ('Generate the pipeline configuration file') rather than actionable guidance with copy-paste-ready templates. | 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 the validation step is only mentioned at the end rather than integrated throughout. For a skill involving deployment (a destructive/risky operation), the lack of rollback verification and intermediate validation caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no bundle files to reference. All content—prerequisites, instructions, error handling, examples, resources—is inlined in a single file. There are no references to separate files for platform-specific templates, deployment scripts, or detailed examples, despite the Output section promising Dockerfiles and Kubernetes manifests. | 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
4801da6
- 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.