| name | ak:deploy |
| description | Deploy projects to any platform with auto-detection. Use when user says "deploy", "publish", "ship", "go live", "push to production", "host this app", or mentions any hosting platform (Vercel, Netlify, Cloudflare, Railway, Fly.io, Render, Heroku, TOSE, Github Pages, AWS, GCP, Digital Ocean, Vultr, Coolify, Dokploy). Auto-detects deployment target from config files and docs/deployment.md. |
| user-invocable | true |
| when_to_use | Invoke when the goal is hosting or publishing an app. |
| category | infrastructure |
| keywords | ["deploy","hosting","Vercel","Netlify","Cloudflare"] |
| license | MIT |
| argument-hint | [platform] [environment] |
| metadata | {"author":"agentkit","version":"1.0.0"} |
Deploy Skill
Auto-detect deployment target and deploy the current project. Supports 15 platforms with cost-optimized recommendations.
Scope
This skill handles: project deployment, platform selection, deployment docs creation/update.
Does NOT handle: infrastructure provisioning, database migrations, DNS management, SSL certificates, CI/CD pipeline creation.
For advanced infrastructure/troubleshooting, activate /ak:devops skill.
Workflow
1. Detect Deployment Target
Check in order (stop at first match):
- Read
docs/deployment.md — if exists, parse platform and config from it
- Scan config files — detect platform from existing configs (see Detection Signals)
- Analyze project type — determine best platform based on project structure
- Ask user — use
ask_user capability with cost-optimized recommendations
2. Detection Signals
| File/Pattern | Platform |
|---|
vercel.json, .vercel/ | Vercel |
netlify.toml, _redirects | Netlify |
wrangler.toml, wrangler.json | Cloudflare |
fly.toml | Fly.io |
railway.json, railway.toml | Railway |
render.yaml | Render |
Procfile + app.json | Heroku |
tose.yaml, tose.json | TOSE.sh |
docker-compose.yml + coolify ref | Coolify |
dokploy.yml | Dokploy |
.github/workflows/*pages* | Github Pages |
app.yaml (GAE format) | GCP |
amplify.yml, |
