Devops
Deploy and operate serverless, containers, and Kubernetes workloads on Cloudflare, Docker, GCP, and K8s with guided platform picks and commands.
Overview
DevOps is an agent skill most often used in Operate (also Ship, Build) that guides deployment and management across Cloudflare, Docker, GCP, and Kubernetes.
Install
npx skills add https://github.com/mrgoonie/claudekit-skills --skill devopsWhat is this skill?
- Platform selection matrix: Workers vs R2 vs D1 vs Docker/Cloud Run vs GKE vs Pages vs Helm
- Quick-start commands for Cloudflare Workers, Docker, Cloud Run, and kubectl apply flows
- Coverage of GitOps (Argo CD, Flux), CI/CD, multi-region deploys, and security audit topics
- Explicit triggers for serverless, containerize, RBAC, and network policies
- Version 2.0.0 MIT skill scoped to Cloudflare, Docker, GCP, and Kubernetes
- 4 primary platform families: Cloudflare, Docker, GCP, Kubernetes
- Platform selection table with 9 common infrastructure needs mapped to tools
Adoption & trust: 792 installs on skills.sh; 2.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You built the product but stall choosing between Workers, Cloud Run, and K8s and fear shipping the wrong hosting or insecure cluster defaults.
Who is it for?
Indie SaaS and API builders shipping containerized or serverless apps who need one skill to compare Cloudflare, GCP, Docker, and Kubernetes options.
Skip if: Pure local-only scripts with no deploy intent, or teams that already enforce a single locked Terraform pipeline with no agent-driven changes.
When should I use this skill?
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes; serverless, containers, CI/CD, GitOps, security audit.
What do I get? / Deliverables
You get a platform-matched deploy path with concrete CLI steps and ops topics (GitOps, CI/CD, security audit) your agent can execute or script next.
- Deployment commands and platform recommendation for the workload
- Kubernetes manifests or GitOps-oriented apply steps
- Security audit and RBAC/network policy guidance outlines
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Production deployment and cluster management are canonical Operate infra work even when first executed at Ship time. Wrangler, gcloud, kubectl, Helm, and GitOps map directly to running and maintaining cloud infrastructure.
Where it fits
Containerize your API with Docker and sketch Cloud Run vs GKE before committing to cluster cost.
Run wrangler deploy or gcloud run deploy for the first production cut with a checklist-style agent walkthrough.
Apply Helm manifests, tune RBAC/network policies, and align GitOps after an incident or scaling change.
Use security audit and multi-region guidance when hardening observability and blast-radius controls post-launch.
How it compares
Multi-cloud deploy playbook—not a single-vendor MCP integration or a frontend styling skill.
Common Questions / FAQ
Who is devops for?
Solo and indie builders using AI coding agents who own deployment, CI/CD, and light security hardening without a dedicated platform team.
When should I use devops?
Use it in Operate (infra) for kubectl, Helm, and GitOps; during Ship (launch) for first production deploy and CI/CD; and in Build (backend/integrations) when containerizing services or wiring Cloudflare Workers alongside your API.
Is devops safe to install?
The skill implies shell, cloud APIs, and production changes—treat outputs as proposals until you review IAM, secrets, and blast radius; check the Security Audits panel on this Prism page before granting your agent deploy credentials.
SKILL.md
READMESKILL.md - Devops
# DevOps Skill Deploy and manage cloud infrastructure across Cloudflare, Docker, Google Cloud, and Kubernetes. ## When to Use - Deploy serverless apps to Cloudflare Workers/Pages - Containerize apps with Docker, Docker Compose - Manage GCP with gcloud CLI (Cloud Run, GKE, Cloud SQL) - Kubernetes cluster management (kubectl, Helm) - GitOps workflows (Argo CD, Flux) - CI/CD pipelines, multi-region deployments - Security audits, RBAC, network policies ## Platform Selection | Need | Choose | |------|--------| | Sub-50ms latency globally | Cloudflare Workers | | Large file storage (zero egress) | Cloudflare R2 | | SQL database (global reads) | Cloudflare D1 | | Containerized workloads | Docker + Cloud Run/GKE | | Enterprise Kubernetes | GKE | | Managed relational DB | Cloud SQL | | Static site + API | Cloudflare Pages | | Container orchestration | Kubernetes | | Package management for K8s | Helm | ## Quick Start ```bash # Cloudflare Worker wrangler init my-worker && cd my-worker && wrangler deploy # Docker docker build -t myapp . && docker run -p 3000:3000 myapp # GCP Cloud Run gcloud run deploy my-service --image gcr.io/project/image --region us-central1 # Kubernetes kubectl apply -f manifests/ && kubectl get pods ``` ## Reference Navigation ### Cloudflare Platform - `cloudflare-platform.md` - Edge computing overview - `cloudflare-workers-basics.md` - Handler types, patterns - `cloudflare-workers-advanced.md` - Performance, optimization - `cloudflare-workers-apis.md` - Runtime APIs, bindings - `cloudflare-r2-storage.md` - Object storage, S3 compatibility - `cloudflare-d1-kv.md` - D1 SQLite, KV store - `browser-rendering.md` - Puppeteer automation ### Docker - `docker-basics.md` - Dockerfile, images, containers - `docker-compose.md` - Multi-container apps ### Google Cloud - `gcloud-platform.md` - gcloud CLI, authentication - `gcloud-services.md` - Compute Engine, GKE, Cloud Run ### Kubernetes - `kubernetes-basics.md` - Core concepts, architecture, workloads - `kubernetes-kubectl.md` - Essential commands, debugging workflow - `kubernetes-helm.md` / `kubernetes-helm-advanced.md` - Helm charts, templates - `kubernetes-security.md` / `kubernetes-security-advanced.md` - RBAC, secrets - `kubernetes-workflows.md` / `kubernetes-workflows-advanced.md` - GitOps, CI/CD - `kubernetes-troubleshooting.md` / `kubernetes-troubleshooting-advanced.md` - Debug ### Scripts - `scripts/cloudflare-deploy.py` - Automate Worker deployments - `scripts/docker-optimize.py` - Analyze Dockerfiles ## Best Practices **Security:** Non-root containers, RBAC, secrets in env vars, image scanning **Performance:** Multi-stage builds, edge caching, resource limits **Cost:** R2 for large egress, caching, right-size resources **Development:** Docker Compose local dev, wrangler dev, version control IaC ## Resources - Cloudflare: https://developers.cloudflare.com - Docker: https://docs.docker.com - GCP: https://cloud.google.com/docs - Kubernetes: https://kubernetes.io/docs - Helm: https://helm.sh/docs # Cloudflare Browser Rendering Headless browser automation with Puppeteer/Playwright on Cloudflare Workers. ## Setup **wrangler.toml:** ```toml name = "browser-worker" main = "src/index.ts" compatibility_date = "2024-01-01" browser = { binding = "MYBROWSER" } ``` ## Basic Screenshot Worker ```typescript import puppeteer from '@cloudflare/puppeteer'; export default { async fetch(request: Request, env: Env): Promise<Response> { const browser = await puppeteer.launch(env.MYBROWSER); const page = await browser.newPage(); await page.goto('https://example.com', { waitUntil: 'networkidle2' }); const screenshot = await page.screenshot({ type: 'png' }); await browser.close(); return new Response(screenshot, {