In short:
ak-deployships your app to the right platform and environment, then checks the URL, health and revision before it calls the job done. Errors it cannot fix go toak-devops, and deploy docs that need changes go throughak-docsupdate. It does not build infrastructure such as servers, DNS, SSL, database migrations or CI/CD pipelines.
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 want to push a new release to production or staging, deploy for the first time without a platform picked, or when the repo has several targets and you worry about pushing to the wrong one. You do not need it when you are only asking about a platform, or when the real job is building infrastructure: that belongs to ak-devops. It supports 15 platforms, from Vercel, Netlify and Cloudflare to self-hosted Coolify and Dokploy.
flowchart LR
A["Code is ready"] --> B["ak-deploy"]
B --> C["App runs, with proof and a rollback command"]
B --> D["Error it cannot fix: ak-devops"]
C --> E["Deploy docs changed: ak-docs update"]Four things it always makes clear:
| Concept | Question | Example |
|---|---|---|
| Deploy target | Which platform, which environment? | /ak-deploy vercel production |
| Docs and config disagree | The docs say one place, a config file says another. Now what? | The docs say Railway, but the repo has fly.toml |
| Proof the deploy worked | What counts as a successful deploy? | The URL responds correctly, the health endpoint returns 200, the revision matches the commit just pushed, the environment is right |
| The project's deploy docs | What gets recorded, and where? | Record the variable name DATABASE_URL and where to get its value, never the value itself |
The skill keeps no price table, so it only gives cost-based advice after checking current prices and limits from official sources.
Sample prompt (project already configured):
/ak-deploy production
The <app name> project already deploys to Vercel.
Done when: the home page and /api/health return 200 on the production URL.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-deploy: ship your app and check it really runs" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-deploy". 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-deploy
