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…
Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure).
Install CD Pipeline Generator
$ npx skills add ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ArabelaTso/Skills-4-SE cd-pipeline-generator --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/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cd-pipeline-generator .claude/skills/cd-pipeline-generator && 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 "cd-pipeline-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generator into .claude/skills/cd-pipeline-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cd-pipeline-generator", 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/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generatorType 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 ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ArabelaTso/Skills-4-SE cd-pipeline-generator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cd-pipeline-generator .agents/skills/cd-pipeline-generator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cd-pipeline-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generator into .agents/skills/cd-pipeline-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cd-pipeline-generator", 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 ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ArabelaTso/Skills-4-SE cd-pipeline-generator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cd-pipeline-generator .cursor/skills/cd-pipeline-generator && 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 "cd-pipeline-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generator into .cursor/skills/cd-pipeline-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cd-pipeline-generator", 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/ArabelaTso/Skills-4-SE.git --path skills/cd-pipeline-generator--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 ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ArabelaTso/Skills-4-SE cd-pipeline-generator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cd-pipeline-generator .gemini/skills/cd-pipeline-generator && 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 "cd-pipeline-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generator into .gemini/skills/cd-pipeline-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cd-pipeline-generator", 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 ArabelaTso/Skills-4-SE cd-pipeline-generatorInstalls 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 ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cd-pipeline-generator .github/skills/cd-pipeline-generator && 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 "cd-pipeline-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generator into .github/skills/cd-pipeline-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cd-pipeline-generator", 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 ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ArabelaTso/Skills-4-SE cd-pipeline-generator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cd-pipeline-generator .opencode/skills/cd-pipeline-generator && 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 "cd-pipeline-generator" agent skill from https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/cd-pipeline-generator into .opencode/skills/cd-pipeline-generator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cd-pipeline-generator", 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
cd-pipeline-generator- GitHub stars
- 253
- Token cost
- ~1.3k tokens
- SKILL.md length
- 398 words
- Files
- 4 (incl. assets)
- Skills in repo
- 170
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure).
- Works in 7 steps: Identify Deployment Target → Select Template → Configure Environments → …
- Setting up continuous deployment pipelines
- SKILL.md covers Overview, Workflow, Template Features and Security Best Practices, plus 2 more sections
- Needs AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
What it does
CD Pipeline Generator is an agent skill from ArabelaTso/Skills-4-SE. Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies. Includes templates for environment-specific deployments with approval gates, secrets management, and rollback capabilities.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including assets (for example `assets/deploy-aws.yml`, `assets/deploy-azure.yml` and `assets/deploy-gcp.yml`).
It sits in DevOps & Cloud, covering Deployment, CI/CD and Secrets management. It works with GitHub Actions, Amazon Web Services, Google Cloud and Microsoft Azure. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.
When your agent uses it
- Setting up continuous deployment pipelines
- Creating deployment automation
- Configuring multi-environment deployment strategies
Example prompts
- “/cd-pipeline-generator”
Requirements
- Python 3
- Docker
- A credential in AWS_SECRET_ACCESS_KEY
- A credential in GCP_SERVICE_ACCOUNT_KEY
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4f38503. 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).
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 these keys or tokens, usually read from environment variables:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYGCP_SERVICE_ACCOUNT_KEYAZURE_CREDENTIALS
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CD Pipeline Generator loads about 1.3k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 398 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 ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 398 words, ~1,313 tokens.
Download SKILL.mdSave it as
.claude/skills/cd-pipeline-generator/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- cd-pipeline-generator
- description
- Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies. Includes templates for environment-specific deployments with approval gates, secrets management, and rollback capabilities.
CD Pipeline Generator
Overview
Generate production-ready GitHub Actions deployment workflows that automate deployments to staging and production environments with environment protection rules, approval gates, and secrets management.
Workflow
1. Identify Deployment Target
Determine the cloud platform and deployment method:
- AWS: ECS, Elastic Beanstalk, EC2, Lambda
- GCP: Cloud Run, App Engine, Compute Engine, Cloud Functions
- Azure: App Service, Container Instances, Functions
2. Select Template
Use the appropriate template from assets/ based on cloud platform:
deploy-aws.yml- AWS deployments (ECS, Elastic Beanstalk, Lambda)deploy-gcp.yml- GCP deployments (Cloud Run, App Engine)deploy-azure.yml- Azure deployments (App Service, Container Instances)
3. Configure Environments
Set up GitHub environment protection rules for staging and production:
Staging environment:
- Auto-deploy on merge to main/master
- No approval required
- Use staging secrets and variables
Production environment:
- Manual approval required
- Deploy on workflow_dispatch or tag push
- Use production secrets and variables
- Optional: Restrict to specific branches
4. Configure Secrets
Add required secrets to GitHub repository settings (Settings → Secrets and variables → Actions):
AWS:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_REGION
GCP:
GCP_PROJECT_IDGCP_SERVICE_ACCOUNT_KEY
Azure:
AZURE_CREDENTIALSAZURE_SUBSCRIPTION_ID
5. Customize Deployment Steps
Adapt the template to project-specific deployment needs:
Build artifacts: Add build steps before deployment
- name: Build application
run: npm run build # or: python -m build, go build, cargo buildDocker images: Build and push container images
- name: Build Docker image
run: docker build -t $IMAGE_NAME:$TAG .
- name: Push to registry
run: docker push $IMAGE_NAME:$TAGDatabase migrations: Run migrations before deployment
- name: Run migrations
run: npm run migrate # or: alembic upgrade head, rails db:migrateHealth checks: Verify deployment success
- name: Health check
run: curl -f https://$DEPLOYMENT_URL/health || exit 16. Set Deployment Triggers
Configure when deployments run:
Staging: Auto-deploy on push to main
on:
push:
branches: [main]Production: Manual trigger or tag-based
on:
workflow_dispatch:
push:
tags:
- 'v*'7. Place Workflow File
Create deployment workflow at .github/workflows/deploy.yml. If multiple deployment workflows are needed (e.g., separate staging and production), use descriptive names:
.github/workflows/deploy-staging.yml.github/workflows/deploy-production.yml
Show full SKILL.md (150 more words)Show less
Template Features
All templates include:
- Environment separation: Distinct staging and production deployments
- Approval gates: Production deployments require manual approval
- Secrets management: Secure credential handling via GitHub secrets
- Deployment status: Clear success/failure reporting
- Rollback support: Easy revert to previous versions
- Conditional execution: Deploy only when tests pass
Security Best Practices
- Never commit credentials or API keys to the repository
- Use GitHub environments to scope secrets appropriately
- Enable required reviewers for production deployments
- Use OIDC authentication instead of long-lived credentials when possible
- Implement deployment windows for production (e.g., business hours only)
- Add deployment notifications to Slack/email
Customization Examples
Add deployment notification:
- name: Notify deployment
if: always()
uses: 8398a7/action-slack@v3
with:
status: ${{ job.status }}
text: 'Deployment to ${{ github.event.inputs.environment }} ${{ job.status }}'
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK }}Add rollback capability:
- name: Rollback on failure
if: failure()
run: |
echo "Deployment failed, rolling back..."
# Platform-specific rollback commandsRestrict production deployment time:
- name: Check deployment window
run: |
HOUR=$(date +%H)
if [ $HOUR -lt 9 ] || [ $HOUR -gt 17 ]; then
echo "Deployments only allowed 9 AM - 5 PM"
exit 1
fiTips
- Start with staging deployments to validate the workflow
- Use environment-specific configuration files (e.g.,
config.staging.json,config.production.json) - Implement blue-green or canary deployments for zero-downtime updates
- Add deployment metrics and monitoring
- Document rollback procedures in the repository
- Test deployment workflows in a separate test environment first
© ArabelaTso, Apache-2.0. 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 3 other files (assets) in skills/cd-pipeline-generator of ArabelaTso/Skills-4-SE.
- SKILL.md
- assets/deploy-aws.yml
- assets/deploy-azure.yml
- assets/deploy-gcp.yml
Open the folder on GitHubat commit 4f38503
Compare with similar skills
CD Pipeline Generator 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 |
|---|---|---|---|---|---|---|
| CD Pipeline Generator this skillArabelaTso/Skills-4-SE | 253 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Azure Bicep Skilltimothywarner-org/claude-code | 224 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Deploying Cloud Deception With Decoy Resourcesmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Kcli Cluster Deploymentkarmab/kcli | 653 | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Sdaf Orientation And SurfaceAzure/sap-automation | 145 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Azure Bicep Skill
timothywarner-org/claude-code
A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.
Deploying Cloud Deception With Decoy Resources
mukul975/Anthropic-Cybersecurity-Skills
Deploy cloud-native deception across AWS, Azure, and GCP using decoy (honey) resources whose only purpose is to generate a high-fidelity alert the instant an attacker touches them: canary IAM access…
Kcli Cluster Deployment
karmab/kcli
Guides deployment and management of Kubernetes clusters with kcli.
- Official
Sdaf Orientation And Surface
Azure/sap-automation
Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate/remove), summarise the three…
Atmos Migration
cloudposse/atmos
Migrate to Atmos from native Terraform, Terraform Workspaces, Terramate, Terragrunt, Make, Just, or Task; migrate tool versions from mise or Aqua CLI; migrate AWS/GCP/Azure CLI configs, Leapp…
More from ArabelaTso/Skills-4-SE
All 170 skills in this repoCve Watchlist Action Recommendation Generator
ArabelaTso/Skills-4-SE
Generate prioritized CVE watchlists and actionable security recommendations for repositories.
Framework Migration Assistant
ArabelaTso/Skills-4-SE
Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).
Metamorphic Test Generator
ArabelaTso/Skills-4-SE
Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.
Reproduction Trace Instrumenter
ArabelaTso/Skills-4-SE
Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.
Spring Mvc To Boot Migrator
ArabelaTso/Skills-4-SE
Automatically migrate Spring MVC applications to Spring Boot.
State Snapshot Instrumenter
ArabelaTso/Skills-4-SE
Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.
Related
Categories
Questions about CD Pipeline Generator
What does CD Pipeline Generator do?
Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). CD Pipeline Generator is an agent skill from ArabelaTso/Skills-4-SE. Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure).
When should I use CD Pipeline Generator?
CD Pipeline Generator fits situations like: setting up continuous deployment pipelines; creating deployment automation; configuring multi-environment deployment strategies.
How do I install CD Pipeline Generator in Claude Code?
Run `npx skills add ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a claude-code`. Or copy the skill folder (skills/cd-pipeline-generator in ArabelaTso/Skills-4-SE) into .claude/skills/cd-pipeline-generator in your project. Claude Code loads it when a task matches its description.
How do I install CD Pipeline Generator in Codex?
Run `npx skills add ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a codex`. Or copy the skill folder (skills/cd-pipeline-generator in ArabelaTso/Skills-4-SE) into .agents/skills/cd-pipeline-generator in your project. Codex loads it when a task matches its description.
Can I use CD Pipeline Generator 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 ArabelaTso/Skills-4-SE --skill cd-pipeline-generator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cd-pipeline-generator, .gemini/skills/cd-pipeline-generator, .github/skills/cd-pipeline-generator and .opencode/skills/cd-pipeline-generator in your project.
What does CD Pipeline Generator need to run?
Going by SKILL.md and its folder, CD Pipeline Generator needs credentials named AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, GCP_SERVICE_ACCOUNT_KEY and AZURE_CREDENTIALS. Our summary lists: Python 3; Docker; A credential in AWS_SECRET_ACCESS_KEY; A credential in GCP_SERVICE_ACCOUNT_KEY.
Does CD Pipeline Generator 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 CD Pipeline Generator 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 CD Pipeline Generator use?
CD Pipeline Generator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CD Pipeline Generator use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to CD Pipeline Generator?
Skills that share tags, products or a category with CD Pipeline Generator: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Azure Bicep Skill (timothywarner-org/claude-code, 224 stars), Deploying Cloud Deception With Decoy Resources (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Kcli Cluster Deployment (karmab/kcli, 653 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CD Pipeline Generator?
ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 170 skills in this directory. The repository was last updated on August 21, 2026.
Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.