deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use this skill when designing zero-downtime deployment pipelines, implementing canary rollout strategies, setting up multi-environment promotion workflows, or debugging failed deployment gates in CI/CD.
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly articulates specific capabilities (pipeline design, approval gates, security checks, deployment orchestration) and provides explicit trigger guidance with a 'Use this skill when...' clause covering four distinct scenarios. The description uses appropriate third-person voice, includes natural domain-specific keywords, and carves out a distinct niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'multi-stage CI/CD pipelines', 'approval gates', 'security checks', 'deployment orchestration', 'canary rollout strategies', 'multi-environment promotion workflows', and 'debugging failed deployment gates'. | 3 / 3 |
Completeness | Clearly answers both 'what' (design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration) and 'when' (explicit 'Use this skill when...' clause listing four specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CI/CD', 'deployment pipelines', 'canary rollout', 'zero-downtime deployment', 'approval gates', 'multi-environment promotion', 'deployment gates'. These cover a good range of terms a user working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around CI/CD pipeline design, deployment orchestration, and canary rollouts. The specific focus on approval gates, zero-downtime deployments, and multi-environment promotion workflows makes it unlikely to conflict with general DevOps or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent executable examples across multiple CI/CD platforms and clear workflow sequencing with validation checkpoints. Its main weakness is verbosity—it includes explanatory content Claude already knows (DORA metrics definitions, basic Docker caching, feature flag concepts) and tries to be a comprehensive reference rather than a lean overview pointing to detailed sub-files. The referenced bundle files don't exist, undermining the progressive disclosure structure.
Suggestions
Trim the Input/Output and When to Use sections significantly—Claude can infer appropriate usage from the content itself; these add ~40 lines of low-value text.
Move deployment strategy details, troubleshooting scenarios, and monitoring/metrics content into separate reference files (e.g., references/deployment-strategies.md, references/troubleshooting.md) to keep SKILL.md as a lean overview with pointers.
Remove explanations of well-known concepts (DORA metric definitions, what feature flags are, Docker layer caching basics) or reduce them to single-line reminders.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~350 lines) and includes some content Claude would already know (e.g., what DORA metrics are, basic Docker layer caching advice, feature flag concepts). The decision table and deployment strategy explanations are useful but the overall document could be tightened significantly—the Input/Output and When to Use sections are verbose, and best practices are mostly general knowledge. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready configurations across multiple CI/CD platforms (GitHub Actions, GitLab CI, Azure Pipelines, Argo Rollouts), concrete bash scripts for verification and rollback, working Python health check code, and specific Kubernetes commands. Every major concept is backed by real configuration. | 3 / 3 |
Workflow Clarity | The pipeline stages are clearly sequenced with an ASCII diagram and numbered breakdown. The GitHub Actions multi-stage example shows explicit job dependencies with validation checkpoints (health check → rollback on failure). The rollback automation includes a proper feedback loop with `if: failure()` triggering undo, and the verify step has retry logic with clear exit conditions. | 3 / 3 |
Progressive Disclosure | The skill references `references/advanced-strategies.md` and related skills, which is good structure. However, no bundle files are provided to back these references, and the main document is quite long with inline content (deployment strategies, troubleshooting, monitoring) that could reasonably be split into separate reference files. The document tries to be both overview and comprehensive reference. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (501 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
112197c
- 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.