DevOps skills for Claude Code and Codex
A practical skill pack for DevOps work in Claude Code and Codex desktop.
This repository ships 31 skills:
- 16 generators for scaffolding production-ready configs
- 14 validators for linting, security checks, and dry-run validation
- 1 debugger (
k8s-debug) for cluster troubleshooting
The goal is simple: make infra and pipeline work faster without skipping correctness checks.
Quick Install
Claude Code Plugin Marketplace
/plugin marketplace add akin-ozer/cc-devops-skills
/plugin install devops-skills@akin-ozer
Codex Desktop
Skills only:
$skill-installer install https://github.com/akin-ozer/cc-devops-skills/tree/main/devops-skills-plugin/skills
Manual plugin install:
- Clone the repo and link the packaged plugin into your local Codex plugin directory:
git clone https://github.com/akin-ozer/cc-devops-skills.git ~/.codex/devops-skills
mkdir -p ~/plugins ~/.agents/plugins
ln -s ~/.codex/devops-skills/devops-skills-plugin ~/plugins/devops-skills
- Create or update
~/.agents/plugins/marketplace.json so Codex can discover the plugin:
{
"name": "local-plugins",
"interface": {
"displayName": "Local Plugins"
},
"plugins": [
{
"name": "devops-skills",
"source": {
"source": "local",
"path": "./plugins/devops-skills"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
}
]
}
If you already use ~/.agents/plugins/marketplace.json, append the devops-skills entry instead of replacing the file.
The packaged Codex manifest lives at devops-skills-plugin/.codex-plugin/plugin.json. It exists alongside the Claude manifest and points at the same skills/ directory.
Team Rollout
Add this to project-level .claude/settings.json:
{
"extraKnownMarketplaces": {
"devops-skills": {
"source": {
"source": "github",
"repo": "akin-ozer/cc-devops-skills"
}
}
}
}
Drop-In GitHub Action Wrapper
This repository also publishes a drop-in wrapper around anthropics/claude-code-action@v1.
Replace:
uses: anthropics/claude-code-action@v1
With:
uses: akin-ozer/cc-devops-skills@v1
Behavior stays compatible with upstream v1, and DevOps skills are injected by default through:
- Marketplace:
https://github.com/akin-ozer/cc-devops-skills.git
- Plugin:
devops-skills@akin-ozer
Tag policy:
akin-ozer/cc-devops-skills@v1 tracks this wrapper's latest v1.x.y release.- The wrapper internally calls
anthropics/claude-code-action@v1 (tag), not a pinned SHA.
To run as pure passthrough (no auto-injection):
uses: akin-ozer/cc-devops-skills@v1
with:
inject_devops_skills: "false"
Docs and examples:
How people use this repo
Most workflows are generator + validator loops.
flowchart LR
A["Ask for generator skill"] --> B["Create artifact"]
B --> C["Run matching validator"]
C --> D{"Passes checks?"}
D -- "No" --> E["Patch + re-run checks"]
D -- "Yes" --> F["Ship to PR/CI"]
Typical prompts:
Use terraform-generator to scaffold a reusable AWS VPC module with outputs and examples.
Validate ./infra/vpc with terraform-validator and list only high-severity findings.
Use k8s-debug to diagnose pods stuck in Pending in namespace payments.
What makes these skills useful
- Local-first validation pipelines: many validator skills run shell/Python checks directly from their
scripts/ folders.
- Tool-aware workflows: validators integrate with real tools like
terraform, tflint, checkov, helm, kubeconform, actionlint, and act.
- CRD/provider documentation lookup: Kubernetes/Helm/Terraform/Terragrunt/Ansible flows include explicit doc lookup paths for custom resources.
- Fallback behavior is defined: when a tool is missing, many skills degrade gracefully and tell you exactly what was skipped.
Skill catalog (31)
Infrastructure as code (6)
