cc-devops-skills
31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker
- 326 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The validators run `terraform`, `helm`, `kubectl`, `actionlint` and `act` on your machine, and `terraform plan` and dry runs reach the cloud and cluster
- The `k8s-debug` debugger reads the state of whichever cluster your `kubectl` points at
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/cc-devops-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The validators run `terraform`, `helm`, `kubectl`, `actionlint` and `act` on your machine, and `terraform plan` and dry runs reach the cloud and cluster
- The `k8s-debug` debugger reads the state of whichever cluster your `kubectl` points at
This is third-party code. Review the repository files before installing.
What it does
cc-devops-skills bundles 31 skills for infrastructure work built around generate-then-validate loops. Sixteen generators create config scaffolds, fourteen validators lint them and check security, and one debugger, `k8s-debug`, troubleshoots cluster failures. The skills are grouped by area. Infrastructure as code: Ansible, Terraform and Terragrunt. CI/CD: Azure Pipelines, GitHub Actions, GitLab CI and Jenkinsfile. Containers and Kubernetes: Dockerfile, Helm and manifests. Observability: Fluent Bit, Loki, LogQL and PromQL. Scripting and build: Bash and Makefile. The validators call real tools. `terraform-validator` runs `terraform fmt`, `tflint`, `terraform validate`, Checkov and an optional `plan`; `helm-validator` runs `helm lint`, `kubeconform` and a cluster dry run. When a needed tool is missing, the skill says what it skipped and carries on.
Who it is for. For DevOps engineers and developers who write Terraform, Helm charts, CI pipelines and Dockerfiles with Claude Code or Codex.
Good fit when
- You need a reusable Terraform module for an AWS network: `terraform-generator` produces a module with variables, outputs and examples
- Before a pull request you want `terraform-validator` to check `./infra/vpc` and list only high-severity findings
- Pods are stuck in Pending in the `payments` namespace: `k8s-debug` runs the diagnosis
- You need to check a GitHub Actions workflow: `github-actions-validator` runs `actionlint` and tests through `act`
- You want infrastructure PR review in CI to run with the skills: use `akin-ozer/cc-devops-skills@v1` in place of `anthropics/claude-code-action@v1`
Not a fit when
- You work in a single area, such as Dockerfile only: the plugin installs whole, with all 31 skills
- The machine lacks `terraform`, `kubectl`, `helm` and other utilities: the skills skip those checks and report it
- You need protection from changes in a production cluster: the `k8s-debug` debugger works with whichever cluster your `kubectl` points at
Example request
Validate ./infra/vpc with terraform-validator and list only high-severity findingsLimitations
You need `bash` and `python3` (3.8 recommended, 3.9 for some security tooling). Other tools are installed per area: `terraform`, `tflint`, `terragrunt` and `checkov` for Terraform; `kubectl`, `kubeconform`, `helm` and `yamllint` for Kubernetes; `hadolint` for Docker; `actionlint` and `act` for GitHub Actions; `shellcheck` for scripts; `promtool` for Prometheus. You do not need them all at once.
For Codex the plugin installs as skills through `$skill-installer` or by hand, linking the plugin folder into the plugins directory. The `plugin.json` manifests are separate for Claude and Codex. The GitHub Actions wrapper mirrors the `anthropics/claude-code-action@v1` interface and calls it internally by tag rather than a pinned SHA.
How to disable. In Claude Code disable the `devops-skills` plugin through `/plugin`. For Codex delete the `~/plugins/devops-skills` link and its entry in `~/.agents/plugins/marketplace.json`. The `inject_devops_skills: "false"` input turns off skill injection in CI.
FAQ
How do I install the DevOps skills in Claude Code?
Run `/plugin marketplace add akin-ozer/cc-devops-skills`, then `/plugin install devops-skills@akin-ozer`. For a team, add an `extraKnownMarketplaces` block with the `akin-ozer/cc-devops-skills` repository to the project's `.claude/settings.json`.
How do I install it in Codex?
For skills only, use `$skill-installer install https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills`. The full plugin installs by hand: clone the repository into `~/.codex/devops-skills`, link `devops-skills-plugin` to `~/plugins/devops-skills` and add an entry to `~/.agents/plugins/marketplace.json`.
What do the validator skills do?
They run real utilities. For example, `github-actions-validator` calls `actionlint` and `act`, `k8s-yaml-validator` goes through `kubeconform` and `kubectl --dry-run`, and `dockerfile-validator` lints and security-checks with `hadolint` and fallback modes.
How do I add the skills to GitHub Actions?
Replace `uses: anthropics/claude-code-action@v1` with `uses: akin-ozer/cc-devops-skills@v1`. Behavior stays compatible with the upstream action, and the skills are injected by default. To turn injection off, set `inject_devops_skills: "false"`.
Which areas does the set cover?
Ansible, Terraform and Terragrunt, Azure, GitHub Actions, GitLab CI and Jenkins pipelines, Dockerfile, Helm and Kubernetes manifests, Fluent Bit, Loki, LogQL, PromQL, plus Bash and Makefile. That makes 31 skills.
Discussion
No questions or reviews yet.
Related
SkillsTerraform Skill
Terraform & OpenTofu Skill for AI Agents
A Terraform and OpenTofu best-practices skill: tests, modules, state, CI/CD and security scanning for AWS, Azure and GCP
KubeShark skill: the agent finds the failure mode first, then writes manifests, Helm and Kustomize to official practice with a rollback plan
A large base of DevOps, security, infrastructure and compliance skills for AI agents
Official HashiCorp skills for Terraform and Packer: HCL style, modules, tests, imports, Stacks, provider development and image builds
A Terraform skill for Claude Code, Codex, Antigravity and Gemini CLI: cuts hallucinations and keeps code on HashiCorp's official practices
Docker Skills
docker-skills
Official Docker skills for agents: Dockerfile and builds, Compose, Sandboxes, Docker Agent and a skill that confirms irreversible actions
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| cc-devops-skills (this entry) | no | 326 | |
| DevOps-Security-Agent-Skills | no | 1,173 | a large base of DevOps, security and compliance skills, while this is 31 skills in generator and validator pairs |
| Terraform Skill | no | 2,423 | one skill of Terraform and OpenTofu best practices, while here Terraform is one area of the set |
| Spellbook | no | 288 | 110 skills for Claude Code and Codex and seven Claude Code agents |
README in short
The description opens with the set's makeup: 31 skills, covering generators, validators and one debugger. It continues with installation for Claude Code and Codex, a team rollout and a GitHub Actions wrapper. The main part is skill tables by area, validator check chains and a list of needed utilities with a macOS install example. It closes with the repository layout and contribution rules.
README badge
Original SKILL.md
--- name: terraform-validator description: Validate, lint, audit, or plan Terraform/.tf/HCL files; runs tflint, checkov, terraform validate. --- # Terraform Validator Comprehensive toolkit for validating, linting, and testing Terraform configurations with automated workflows for syntax validation, security scanning, and intelligent documentation lookup. ## ⚠️ Critical Requirements Checklist **STOP: You MUST complete these steps in order. Do NOT skip any REQUIRED step.** | Step | Action | Required | |------|--------|----------| | 1 | Run `bash scripts/extract_tf_info_wrapper.sh <path>` | ✅ REQUIRED | | 2 | Context7 lookup for **ALL** providers (explicit AND implicit); **WebSearch fallback if not found** | ✅ REQUIRED | | 3 | **READ** `references/security_checklist.md` | ✅ REQUIRED | | 4 | **READ** `references/best_practices.md` | ✅ REQUIRED | | 5 | Run `terraform fmt` | ✅ REQUIRED | | 6 | Run `tflint` (or note as skipped if unavailable) | Recommended | | 7 | Run `terraform init` (if not initialized) | ✅ REQUIRED | | 8 | Run `terraform validate` | ✅ REQUIRED | | 9 | Run `bash scripts/run_checkov.sh <path>` | ✅ REQUIRED | | 10 | Cross-reference findings with `security_checklist.md` sections | ✅ REQUIRED |