devops-automator — Claude Code skill: CI/CD, Terraform, Kubernetes
devops-automator — a skill that turns your AI coder into a DevOps engineer: designs pipelines, writes Terraform and Kubernetes configs, sets up GitOps. Use it when building infrastructure or automating deployments.
MIT 219 installs ★ 274 updated 2026-09-06
npx skills add curiositech/some_claude_skills --skill devops-automator -a claude-codeWhat devops-automator does
devops-automator activates on keywords like CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, and ArgoCD. It operates via file tools (Read, Write, Edit) and runs commands through Bash for Docker, kubectl, and Terraform.
The skill includes ready-made CI/CD patterns, IaC modules, Kubernetes manifests, Helm charts, and Docker configurations. It recognises 15 common pitfalls: hardcoded secrets, YAML duplication, missing resource limits, containers running as root, no health checks. Helps you pick a deployment strategy (Blue/Green, Canary, Rolling) and implement automated rollback.
Out of scope: application code (language skills handle that), database design (data-pipeline-engineer), API design (api-architect). Requires Docker, kubectl, Terraform, and GitHub CLI in your PATH — the skill calls them but does not install them.
What it helps with
- design a CI/CD pipeline with build, test, and deployment stages
- write Terraform modules for cloud infrastructure
- create Kubernetes manifests with autoscaling and health checks
- configure GitOps on ArgoCD with continuous sync
- identify and fix security issues in infrastructure configs
Example prompts for the agent
- Write a GitHub Actions workflow to build a Docker image and deploy to Kubernetes
- Create a Terraform module for an EKS cluster with three nodes and Auto Scaling
- Help me set up ArgoCD to sync my application from a config repository
How to install devops-automator
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill devops-automator -a claude-code2Manually: put the files in place
~/.claude/skills/devops-automator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/devops-automator/
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill devops-automator -a codex2Manually: put the files in place
.agents/skills/devops-automator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill devops-automator -a cursor2Manually: put the files in place
.cursor/skills/devops-automator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install curiositech/some_claude_skills .claude/skills/devops-automator2Manually: put the files in place
.github/skills/devops-automator/SKILL.md1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill devops-automator -a gemini-cli2Platform CLI
gemini skills install https://github.com/curiositech/some_claude_skills --path .claude/skills/devops-automatorManually: put the files in place
.devin/skills/devops-automator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill devops-automator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about devops-automator
How do I install devops-automator in Claude Code?
Run npx skills add curiositech/some_claude_skills --skill devops-automator -a claude-code, then open ~/.claude/skills/devops-automator/SKILL.md.
What does devops-automator do?
It designs and writes CI/CD pipelines, Terraform code, and Kubernetes manifests. Helps you choose deployment strategies, set up GitOps, and avoid common infrastructure mistakes.
What tools do I need for this skill to work?
Docker, kubectl, Terraform, and GitHub CLI must be installed and in your PATH. The skill invokes them via Bash but does not install them.
Source text
SKILL.md · MIT
---
name: devops-automator
description: 'Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline,
infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use data-pipeline-engineer), API design (use api-architect).'
allowed-tools: Read,Write,Edit,Bash(docker:*,kubectl:*,terraform:*,helm:*,gh:*)
metadata:
category: DevOps & Site Reliability
pairs-with:
- skill: site-reliability-engineer
reason: Ensure deployed code is healthy
- skill: security-auditor
reason: Secure the deployment pipeline
tags:
- ci-cd
- terraform
- docker
- kubernetes
- gitops
---
# DevOps Automator
Expert DevOps engineer specializing in CI/CD pipelines, infrastructure as code, container orchestration, and deployment automation.
## Activation Triggers
**Activate on:** "CI/CD", "GitHub Actions", "deployment pipeline", "Terraform", "infrastructure as code", "IaC", "Docker", "Kubernetes", "K8s", "Helm", "container orchestration", "GitOps", "ArgoCD", "deployment automation", "secrets management", "monitoring setup"
**NOT for:** Application development → language skills | Database design → `data-pipeline-engineer` | API design → `api-architect`
## Quick Start
1. **Define deployment strategy**: Blue/Green, Canary, or Rolling
2. **Choose IaC tool**: Terraform for cloud resources, Helm for K8s apps
3. **Design CI stages**: lint → test → security scan → build → deploy
4. **Implement GitOps**: Config repo synced by ArgoCD
5. **Add observability**: Prometheus metrics, structured logging
## Core Capabilities
| Domain | Tools & Technologies |
|--------|---------------------|
| **CI/CD** | GitHub Actions, GitLab CI, Jenkins |
| **IaC** | Terraform, AWS CDK, Pulumi |
| **Containers** | Docker, Kubernetes, Helm |
| **GitOps** | ArgoCD, Flux, Kustomize |
| **Monitoring** | Prometheus, Grafana, ELK/EFK |
## Architecture Patterns
### CI/CD Pipeline Flow
```
Code Commit → Build → Test → Security Scan → Package
↓
Monitor ← Release Staging ← Smoke Tests ← Deploy Dev
↓
Manual Approval
↓
Deploy Production
```
### GitOps Architecture
```
App Repo ──CI──▶ Config Repo ──ArgoCD──▶ K8s Cluster
▲ │
└────Continuous Sync─────┘
```
## Reference Files
Full working examples are in `./references/`:
| File | Description | Lines |
|------|-------------|-------|
| `github-actions-patterns.yaml` | Complete CI/CD pipeline | 217 |
| `terraform-eks-module.tf` | Production EKS cluster | 282 |
| `kubernetes-deployment.yaml` | Deployment + HPA + ArgoCD | 200 |
| `dockerfile-multistage.dockerfile` | Optimized multi-stage build | 51 |
## Anti-Patterns (AVOID These)
### 1. YAML Copy-Paste Proliferation
**Symptom**: Nearly identical workflow files duplicated across repositories
**Fix**: Reusable workflows, Helm charts, Kustomize bases, Terraform modules
### 2. Hardcoded Secrets in Code
**Symptom**: API keys, passwords committed to git
**Fix**: Secret managers (Vault, AWS SM), sealed secrets, env vars from secure sources
### 3. No Rollback Strategy
**Symptom**: No plan for deployment failure, manual intervention required
**Fix**: Blue/green, canary with automated rollback, ArgoCD auto-revert
### 4. Monolithic CI Pipeline
**Symptom**: Single 45-minute pipeline rebuilding everything on every commit
**Fix**: Parallel jobs, caching, incremental builds, path-based triggers
### 5. No Resource Limits
**Symptom**: K8s pods without CPU/memory limits consuming all host resources
**Fix**: Always set requests/limits, use LimitRanges and ResourceQuotas
### 6. Running as Root in Containers
**Symptom**: Dockerfile without USER instruction, pods running privileged
**Fix**: Add USER instruction, set securityContext.runAsNonRoot: true
### 7. Using :latest Tags
**Symptom**: `FROM node:latest` or `image: app:latest` in production
**Fix**: Pin specific versions, use immutable tags with SHA digests
### 8. No Health Checks
**Symptom**: Missing HEALTHCHECK in Dockerfile, no liveness/readiness probes
**Fix**: Add health endpoints, configure probes with appropriate timeouts
### 9. Single Point of Failure
**Symptom**: replicas: 1, no pod anti-affinity, single availability zone
**Fix**: Multiple replicas, pod anti-affinity, topology spread constraints
### 10. Terraform State in Local File
**Symptom**: `terraform.tfstate` committed to git or stored locally
**Fix**: Remote backend (S3+DynamoDB, Terraform Cloud, GCS)
### 11. No Concurrency Control
**Symptom**: Multiple CI runs for same branch, deployment race conditions
**Fix**: Use concurrency groups, implement deployment locks
### 12. Ignoring Security Scanning
**Symptom**: No vulnerability scanning, no secret detection in CI
**Fix**: Trivy, Snyk, or Grype for vulnerabilities; TruffleHog for secrets
### 13. No Drift Detection
**Symptom**: Manual changes to infrastructure, config diverges from code
**Fix**: ArgoCD diff detection, `terraform plan` in CI, regular audits
### 14. Overly Permissive IAM
**Symptom**: IAM roles with `*` actions, service accounts with cluster-admin
**Fix**: Principle of least privilege, IRSA for pods, audit permissions
### 15. No Observability
**Symptom**: No metrics, logs only on stdout, no alerting
**Fix**: Export metrics, structured logging, define SLOs, configure alerts
## Validation Script
Run `./scripts/validate-devops-skill.sh` to check:
- GitHub Actions workflows for deprecated actions, missing caching
- Dockerfiles for security best practices
- Kubernetes manifests for resource limits, security contexts
- Terraform for version constraints, sensitive defaults
## Quality Checklist
```
[ ] All secrets in secret management (not in code)
[ ] Resource limits defined for all containers
[ ] Health checks configured (liveness, readiness)
[ ] Horizontal pod autoscaling enabled
[ ] Security contexts set (non-root, read-only)
[ ] Monitoring and alerting configured
[ ] Rollback strategy documented
[ ] Multi-environment support (dev, staging, prod)
[ ] Concurrency controls in CI pipelines
[ ] Remote state backend for Terraform
[ ] Vulnerability scanning in pipeline
[ ] Version pinning for all dependencies
```
## Output Artifacts
1. **CI/CD Workflows** - GitHub Actions, GitLab CI configs
2. **Terraform Modules** - Reusable infrastructure components
3. **Kubernetes Manifests** - Deployments, services, configs
4. **Helm Charts** - Packaged applications
5. **Docker Configurations** - Optimized multi-stage builds
6. **ArgoCD Applications** - GitOps deployment definitions
## Tools Available
- `Read`, `Write`, `Edit` - File operations for configs and manifests
- `Bash(docker:*)` - Build and manage containers
- `Bash(kubectl:*)` - Kubernetes operations
- `Bash(terraform:*)` - Infrastructure provisioning
- `Bash(helm:*)` - Helm chart management
- `Bash(gh:*)` - GitHub CLI operations
© curiositech · MIT · curiositech/some_claude_skills