devops-engineer
An agent skill by Jeffallan, from Jeffallan/claude-skills. Tags: automation, cli, devops, docker, kubernetes, terraform.
What it does
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing applications, managing infrastructure as code, deploying to Kubernetes clusters, configuring cloud platforms, automating releases, or responding to production incidents. Invoke for pipelines, Docker, Kubernetes, GitOps, Terraform, GitHub Actions, on-call, or platform engineering.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add Jeffallan/claude-skills --skill devops-engineer
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/Jeffallan/claude-skills
cp -r claude-skills/skills/devops-engineer ~/.claude/skills/devops-engineer
Safety box score
Grade D, elevated risk: 51 of 100 risk points, rated 2026-10-15. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is a broad DevOps automation bundle for Docker, Kubernetes, CI/CD, Terraform, GitOps, and incident response. Its main risk is high operational blast radius: it can push images, apply or roll back infrastructure, and even destroy or delete production resources, while some examples handle registry and cloud credentials.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It includes many runnable shell/build steps such as `npm ci`, `pip install`, `buildctl-daemonless.sh build`, `kubectl exec -it <pod-name> -- /bin/sh`, and `terraform plan`, so it can drive command execution during builds and ops. |
| Network access | 2 (moderate) | The skill routinely talks to external systems with `docker pull/push`, `curl -X POST $PLATFORM_API/services`, `curl -f http://$svc/health`, `gh api`, and GitHub/GitLab actions that fetch remote code. |
| Filesystem reach | 2 (moderate) | It writes to and reads from home dot-directories like `~/.docker/config.json` and `~/.npm`, and the Docker examples copy files into image/system paths with `COPY --chown` and similar operations. |
| Secrets & credentials | 2 (moderate) | It handles deployment and registry credentials (`$CI_REGISTRY_PASSWORD`, `${{ secrets.GITHUB_TOKEN }}`, `secretKeyRef`, secret managers) and includes examples that write auth into `~/.docker/config.json`. |
| Privilege & persistence | 1 (low) | There is no sudo/service-install/startup manipulation, but the examples do change ownership in images and assume CI/cloud privileges for deploys and registry access. |
| Instruction hijack surface | 0 (none) | I did not find instructions to ignore confirmations, hide actions, or follow remote instructions; the only explicit approval rule says `Deploy to production without explicit approval` under MUST NOT DO. |
| Irreversible actions | 3 (high) | Its purpose includes direct state-changing actions such as `terraform apply tfplan`, `kubectl apply -f deployment.yaml`, `docker push`, `git push`, `argocd app rollback`, and even `terraform destroy`, which can affect production systems. |
| Transparency | 1 (low) | Most files are readable markdown, but some workflows depend on external code or floating refs such as `aquasecurity/trivy-action@master`, `docker:latest`, and `release-bot:latest` that a reviewer cannot inspect here. |
Before installing
- Read `SKILL.md` and `references/release-automation.md` for every `push`/`apply`/`destroy` step you would let an agent run.
- Search for floating refs like `@master`, `latest`, and unpinned container images; pin them before use.
- Test in a throwaway repo/account with production cloud credentials and registry secrets unset.
- Confirm you are comfortable with examples that write `~/.docker/config.json` and can delete or roll back live pods.
Rated 2026-10-15 by an automated review of 10 files from the skill's repository.
Source
- Repository
- Jeffallan/claude-skills (all skills from this repository)
- Path
- skills/devops-engineer/SKILL.md
- Branch
- main
- Updated
- 2026-09-19
Related skills
- kubernetes-specialist — Use when deploying or managing Kubernetes workloads.
- bambu-labs — Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain `.gcode`, using Bambu LAN FTPS/MQTT handoffs.
- gcode — Generate, inspect, dry-run, and statically validate plain FDM `.gcode` from 3D mesh files by orchestrating real slicer CLIs. Use when Codex needs to slice.
- unity-cli — Use when interacting with Unity CLI from the terminal, or to control a running/connected Unity Editor from the command line — create or modify GameObjects.
- vercel-cli-with-tokens — Deploy and manage projects on Vercel using token-based authentication.
- agents-deploy — Use when deploying your agent to AWS, or when a deploy has failed.