Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration.
Install Deployment Pipeline Design
$ npx skills add wshobson/agents --skill deployment-pipeline-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wshobson/agents deployment-pipeline-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/cicd-automation/skills/deployment-pipeline-design .claude/skills/deployment-pipeline-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deployment-pipeline-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-design into .claude/skills/deployment-pipeline-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-pipeline-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wshobson/agents --skill deployment-pipeline-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wshobson/agents deployment-pipeline-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/cicd-automation/skills/deployment-pipeline-design .agents/skills/deployment-pipeline-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deployment-pipeline-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-design into .agents/skills/deployment-pipeline-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-pipeline-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wshobson/agents --skill deployment-pipeline-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wshobson/agents deployment-pipeline-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/cicd-automation/skills/deployment-pipeline-design .cursor/skills/deployment-pipeline-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deployment-pipeline-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-design into .cursor/skills/deployment-pipeline-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-pipeline-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wshobson/agents.git --path plugins/cicd-automation/skills/deployment-pipeline-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wshobson/agents --skill deployment-pipeline-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wshobson/agents deployment-pipeline-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/cicd-automation/skills/deployment-pipeline-design .gemini/skills/deployment-pipeline-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deployment-pipeline-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-design into .gemini/skills/deployment-pipeline-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-pipeline-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wshobson/agents deployment-pipeline-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wshobson/agents --skill deployment-pipeline-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/cicd-automation/skills/deployment-pipeline-design .github/skills/deployment-pipeline-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deployment-pipeline-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-design into .github/skills/deployment-pipeline-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-pipeline-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wshobson/agents --skill deployment-pipeline-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wshobson/agents deployment-pipeline-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/cicd-automation/skills/deployment-pipeline-design .opencode/skills/deployment-pipeline-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deployment-pipeline-design" agent skill from https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/deployment-pipeline-design into .opencode/skills/deployment-pipeline-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-pipeline-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deployment-pipeline-design- GitHub stars
- 40k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 545 words
- Files
- 3 (incl. references)
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration.
- Designing zero-downtime deployment pipelines
- SKILL.md covers Purpose, Input / Output, When to Use and Detailed patterns and worked…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Implementing canary rollout strategies
What it does
Deployment Pipeline Design is an agent skill from wshobson/agents. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/advanced-strategies.md` and `references/details.md`).
It sits in DevOps & Cloud, covering CI/CD and Deployment. The repository describes itself as: Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi. The licence is MIT.
When your agent uses it
- Designing zero-downtime deployment pipelines
- Implementing canary rollout strategies
- Setting up multi-environment promotion workflows
- Debugging failed deployment gates in CI/CD
Example prompts
- “/deployment-pipeline-design”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, dockerfile and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deployment Pipeline Design loads about 1.4k tokens when it runs, and up to ~8.4k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 545 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 545 words, ~1,379 tokens.
Download SKILL.mdSave it as
.claude/skills/deployment-pipeline-design/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- deployment-pipeline-design
- description
- 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.
Deployment Pipeline Design
Architecture patterns for multi-stage CI/CD pipelines with approval gates, deployment strategies, and environment promotion workflows.
Purpose
Design robust, secure deployment pipelines that balance speed with safety through proper stage organization, automated quality gates, and progressive delivery strategies. This skill covers both the structural design of pipeline architecture and the operational patterns for reliable production deployments.
Input / Output
What You Provide
- Application type: Language/runtime, containerized or bare-metal, monolith or microservices
- Deployment target: Kubernetes, ECS, VMs, serverless, or platform-as-a-service
- Environment topology: Number of environments (dev/staging/prod), region layout, air-gap requirements
- Rollout requirements: Acceptable downtime, rollback SLA, traffic splitting needs, canary vs blue-green preference
- Gate constraints: Approval teams, required test coverage thresholds, compliance scans (SAST, DAST, SCA)
- Monitoring stack: Prometheus, Datadog, CloudWatch, or other metrics sources used for automated promotion decisions
What This Skill Produces
- Pipeline configuration: Stage definitions, job dependencies, parallelism, and caching strategy
- Deployment strategy: Chosen rollout pattern with annotated configuration (canary weights, blue-green switchover, rolling parameters)
- Health check setup: Shallow vs deep readiness probes, post-deployment smoke test scripts
- Gate definitions: Automated metric thresholds and manual approval workflows
- Rollback plan: Automated rollback triggers and manual runbook steps
When to Use
- Design CI/CD architecture for a new service or platform migration
- Implement deployment gates between environments
- Configure multi-environment pipelines with mandatory security scanning
- Establish progressive delivery with canary or blue-green strategies
- Debug pipelines where stages succeed but production behavior is wrong
- Reduce mean time to recovery by automating rollback on metric degradation
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Troubleshooting
Health check passes in pipeline but service is unhealthy in production
The pipeline health check is hitting a shallow /ping endpoint that returns 200 even when the database is unreachable. Use a deep readiness check that verifies actual dependencies (see Health Checks section above).
Show full SKILL.md (237 more words)Show less
Canary deployment never promotes to 100%
Argo Rollouts requires a valid AnalysisTemplate to auto-promote. If the Prometheus query returns no data (e.g., metric name changed), the analysis stays inconclusive and promotion stalls. Add inconclusiveLimit so the rollout fails fast rather than hanging:
spec:
metrics:
- name: error-rate
failureCondition: "result[0] > 0.05"
inconclusiveLimit: 2 # fail after 2 inconclusive results, not hang indefinitely
provider:
prometheus:
query: |
sum(rate(http_requests_total{status=~"5.."}[2m]))
/ sum(rate(http_requests_total[2m]))Staging deploy succeeds but production job never starts
Check that production environment protection rules are configured — a missing reviewer assignment means the approval gate waits indefinitely with no notification. In GitHub Actions, ensure Required reviewers is set to an existing user or team in Settings → Environments → production.
Docker layer cache busted on every run causing slow builds
If COPY . . appears before dependency installation, any source file change invalidates the dependency layer. Reorder to copy dependency manifests first:
# Good: dependencies cached separately from source code
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run buildRollback leaves database migrations applied to old code
A service rollback without a migration rollback causes schema/code mismatch errors. Always make migrations backward-compatible (additive only) for at least one release cycle, and keep undo scripts versioned alongside the migration:
# migrations/V20240315__add_nullable_column.sql (forward)
# migrations/V20240315__add_nullable_column.undo.sql (backward)Never run destructive migrations (DROP COLUMN, ALTER NOT NULL) until the old code version is fully retired from all environments.
Advanced Topics
For platform-specific pipeline configurations, multi-region promotion workflows, and advanced Argo Rollouts patterns, see:
references/advanced-strategies.md— Extended YAML examples, platform-specific configs (GitHub Actions, GitLab CI, Azure Pipelines), multi-region canary patterns, and database migration rollback strategies
Related Skills
github-actions-templates- For GitHub Actions implementation patterns and reusable workflowsgitlab-ci-patterns- For GitLab CI/CD pipeline implementationsecrets-management- For secrets handling in CI/CD pipelines
© wshobson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in plugins/cicd-automation/skills/deployment-pipeline-design of wshobson/agents.
- SKILL.md
- references/advanced-strategies.md
- references/details.md
Open the folder on GitHubat commit 46891e7
Compare with similar skills
Deployment Pipeline Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deployment Pipeline Design this skillwshobson/agents | 40k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Use Vercel Actionamondnet/vercel-action | 764 | — | ~2.7k | Automated safety check: Pass | MIT | |
| CI CD And Automationdzhalaevd/Donatello | 135 | 7 repos | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template | 786 | — | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
Use Vercel Action
amondnet/vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
CI CD And Automation
dzhalaevd/Donatello
Automates CI/CD pipeline setup. An agent skill from dzhalaevd/Donatello.
Prepare Cloudflare Production Deployment
LubomirGeorgiev/cloudflare-workers-nextjs-saas-template
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.
- Official
Deployments Cicd
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
More from wshobson/agents
All 142 skills in this repoCloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
Billing Automation
wshobson/agents
Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.
Python Performance Optimization
wshobson/agents
Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.
Bats Shell Testing Patterns
wshobson/agents
Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.
Distributed Tracing
wshobson/agents
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.
Prompt Engineering Patterns
wshobson/agents
Reference for designing and tuning production LLM prompts: few-shot examples, chain-of-thought, structured outputs, templates and system prompts.
Related
Categories
Questions about Deployment Pipeline Design
What does Deployment Pipeline Design do?
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Deployment Pipeline Design is an agent skill from wshobson/agents. Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration.
When should I use Deployment Pipeline Design?
Deployment Pipeline Design fits situations like: designing zero-downtime deployment pipelines; implementing canary rollout strategies; setting up multi-environment promotion workflows; debugging failed deployment gates in CI/CD.
How do I install Deployment Pipeline Design in Claude Code?
Run `npx skills add wshobson/agents --skill deployment-pipeline-design -a claude-code`. Or copy the skill folder (plugins/cicd-automation/skills/deployment-pipeline-design in wshobson/agents) into .claude/skills/deployment-pipeline-design in your project. Claude Code loads it when a task matches its description.
How do I install Deployment Pipeline Design in Codex?
Run `npx skills add wshobson/agents --skill deployment-pipeline-design -a codex`. Or copy the skill folder (plugins/cicd-automation/skills/deployment-pipeline-design in wshobson/agents) into .agents/skills/deployment-pipeline-design in your project. Codex loads it when a task matches its description.
Can I use Deployment Pipeline Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill deployment-pipeline-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deployment-pipeline-design, .gemini/skills/deployment-pipeline-design, .github/skills/deployment-pipeline-design and .opencode/skills/deployment-pipeline-design in your project.
What does Deployment Pipeline Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Deployment Pipeline Design is instructions for the agent only. Our summary lists: Docker.
Does Deployment Pipeline Design access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Deployment Pipeline Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Deployment Pipeline Design use?
Deployment Pipeline Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deployment Pipeline Design use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.1k tokens, read only when the agent opens those files.
What are the alternatives to Deployment Pipeline Design?
Skills that share tags, products or a category with Deployment Pipeline Design: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars), Use Vercel Action (amondnet/vercel-action, 764 stars) and CI CD And Automation (dzhalaevd/Donatello, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deployment Pipeline Design?
wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,314 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.
Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.