In short:
ak-devopsdeploys, packages containers and changes infrastructure on Cloudflare, Docker, Google Cloud and Kubernetes, at the level you pick. When the work changes an operational route, it hands the guide update toak-docs. It does not switch you to another provider on its own, and it does not print secrets to the output.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it when you need to put an app online, package it with Docker, ship to Cloud Run, upgrade a Helm chart or move DNS. You do not need it when the work is only app code and does not touch build, deploy or infrastructure.
flowchart LR
A["Need to deploy or change infrastructure"] --> B["ak-devops"]
B --> C["Run local, preview or production"]
C --> D["Done, stop"]
C --> E["Operational route changed"]
E --> F["ak-docs updates the guide"]Each run, it needs these to be clear:
| Concept | Question | Example |
|---|---|---|
| Platform and task | Which platform are you on, and what is the job? | /ak-devops cloudflare deploy Worker api to the staging environment |
| Impact level | Only try it locally, go to a preview, or push straight to production? | "Only build and run Docker locally" means it calls no cloud CLI at all. |
| Lock in before production | Which account, project, region? How do you check health and roll back? | Region asia-southeast1, /healthz returns 200, roll back to the previous version on failure. |
| Route changes mean doc changes | Does it change the deploy target, logs, credentials, webhook, OAuth, DNS, backup or rollback? | Moving a domain to Cloudflare means the ops guide must record the new DNS records. |
For Kubernetes and Helm, the skill ships no docs of its own and relies on the official docs of those two projects.
Sample prompt (review the Dockerfile, run locally only):
/ak-devops docker Review the Dockerfile of <app name> and make the image smaller and safer.
Only build and run locally with Docker Compose, do not deploy.
Done when: docker compose up works and the app answers on port 3000.This skill has no flags.
Below is the detailed version: the run flow, 5 situations with prompts, the change history by ak release, and common pitfalls. The detailed version and the interactive page are for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-devops: deploy and run infrastructure on the platform you already use" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-devops". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 22/10/2026
- Licence
- All rights reserved
- Slug
- ak-devops
