agentsclimarketplace

Devops

Skill vanducng/skills/skills/devops

Deployment and infrastructure operations. Use when writing or debugging a Dockerfile, docker build/run, docker compose; running terraform plan/apply/destroy or editing .tf files and modules; using kubectl, debugging pods (CrashLoopBackOff, ImagePullBackOff, OOMKilled), applying manifests, or writing Helm charts; deploying to GKE/EKS/AKS, Cloud Run, or App Engine; GitOps with Argo CD or Flux; writing GitHub Actions CI/CD workflows; or deploying Cloudflare Workers/Pages/R2/D1. Triggers on: dockerfile, docker compose, terraform, tofu, kubectl, k8s, helm, gcloud, eksctl, argocd, wrangler, github actions, ci/cd pipeline, container, cluster, rollout, image scan.From its SKILL.md

Install
npx -y skills add vanducng/skills --skill devops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 8 commands, including `terraform plan` and 7 more.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.5 KB, 692 tokens by cl100k_base, as published. Nobody here has run it

DevOps

Deployment and infrastructure operations across containers, orchestration, IaC, cloud platforms, and CI/CD. SKILL.md dispatches; open the reference that matches the task. Distilled operational guidance - verify exact flags against the current tool docs, and never run a destructive command (terraform apply, kubectl delete, docker system prune) without confirming scope.

When to open which reference

TaskOpen
Dockerfile, multi-stage build, docker build/run, docker compose, image size/security, .dockerignorereferences/docker.md
kubectl commands, pod debugging (CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending), manifests, rollouts, Helm charts, RBAC/secretsreferences/kubernetes.md
terraform/tofu plan/apply/destroy, state, modules, workspaces, remote backends, driftreferences/terraform.md
GKE/EKS/AKS clusters, Cloud Run, App Engine, gcloud, eksctl, Cloudflare Workers/Pages/R2/D1references/cloud-platforms.md
GitHub Actions workflows, GitOps (Argo CD, Flux), deployment strategies, multi-regionreferences/cicd-gitops.md

Operating principles (apply everywhere)

  1. Plan before apply. Always terraform plan / kubectl apply --dry-run=client / docker build before the mutating step. Read the diff.
  2. Least privilege. Non-root containers, scoped RBAC, per-job CI permissions, per-environment secrets. Never bake credentials into images or commit them.
  3. Everything is code and versioned. Dockerfiles, manifests, .tf, Helm values, workflows - all in git, reviewed, applied through CI/GitOps rather than by hand.
  4. Pin versions. No latest image tags, no @master actions - pin digests/major versions for reproducibility.
  5. Right-size resources. Set CPU/memory requests and limits; unbounded workloads get OOM-killed or evicted.
  6. Debug top-down. Overview (get/ps) → details (describe/inspect/events) → logs. Read the error before changing anything.
  7. Scan and observe. Image scanning (Trivy, docker scout), health checks/probes, and metrics/logs are part of "done," not extras.

Quick start

# Docker
docker build -t myapp:1.0 . && docker run -d -p 8080:3000 myapp:1.0

# Kubernetes
kubectl apply -f manifests/ --dry-run=client && kubectl apply -f manifests/ && kubectl rollout status deploy/myapp

# Terraform
terraform init && terraform plan -out=tfplan && terraform apply tfplan

# GCP Cloud Run
gcloud run deploy my-service --image gcr.io/PROJECT/img:tag --region us-central1

# Cloudflare Worker
wrangler deploy

What ships with it: 5 files

18.6 KB alongside SKILL.md

Gives 1 of the 12 instructions most containers cloud skills give in 692 tokens

Counted across 607 of the 705 authors here whose files we hold, read 2026-09-06

  • Run as non-root userin 34 of 607, across 27 files
  • Use multi-stage buildsin 29 of 607
  • Set resource requests and limitsin 24 of 607, across 20 files
  • Configure liveness and readiness probesin 18 of 607, across 14 files
  • Use named volumes for persistent datain 14 of 607, across 9 files
  • Pin base image versionsin 14 of 607
  • Set up environment variablesin 14 of 607, across 10 files
  • Pin provider versionshere, and in 14 of 607
  • Apply least privilege RBAC permissionsin 10 of 607, across 7 files
  • Create a dockerignore filein 10 of 607
  • Use remote state with lockingin 9 of 607
  • Pin base images by digestin 9 of 607, across 8 files

Said here and by no other author read

  • Version everything as code
  • Debug top-down
  • Scan and observe

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.