← All skills
hyper-deploy
79 / 100 · Review before installing
Check before installing. Some of what it can do is expected: a devops skill usually runs commands, installs tools and uses cloud credentials.
By hashgraph-online/awesome-codex-plugins (GitHub) · devops · 1,556 stars · scanned at commit 4070676
[Hyper] Use this skill when the user asks to deploy an app or service, set up a first deployment, change an existing deployment's configuration, diagnose and fix a failed or unhealthy deployment, or prove a repository is deploy-ready with lint, typecheck, and build checks - on Railway, Cloudflare, a Docker image, docker-compose, or a VPS. It detects the target from repository files, applies the matching target guide bundled in this skill, gates production, rollback, and data actions behind expl…
Works with any agent that supports SKILL.md skills.
What this skill can do
Downloads and installs other software
The author does not mention this. Expected for a devops skill.
Found in 30 places.
Show 17 more
- plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 90
npx --no-install wrangler deploy --env staging --strict --dry-run - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 91
npx --no-install wrangler deploy --env staging --strict - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 102
npx --no-install wrangler versions upload --tag "$GIT_SHA" --message "$MSG" - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 103
npx --no-install wrangler versions deploy <NEW_ID>@10% <OLD_ID>@90% -y - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 104
npx --no-install wrangler versions deploy <NEW_ID>@100% -y - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 116
npx --no-install wrangler deployments status --json - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 117
npx --no-install wrangler versions list --json - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 119
npx --no-install wrangler tail --format json --status error --version-id <ID> - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 129
npx --no-install wrangler containers instances <APP_ID> --json - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.ko.md, line 167
npx --no-install wrangler rollback [<VERSION_ID>] --message "rollback: <reason>" - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 55
Next.js: the framework guide recommends `vinext` (a Vite plugin, still beta) for new applications, through `npx vinext check`, `npx vinext init`, then `npx @vin - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 76
npx --no-install wrangler whoami --json - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 87
Run the project-local binary (`npx --no-install wrangler`, or the `wrangler` in `node_modules/.bin`) and read its `--help`; do not fall back to a global install - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 90
npx --no-install wrangler deploy --env staging --strict --dry-run - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 91
npx --no-install wrangler deploy --env staging --strict - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 102
npx --no-install wrangler versions upload --tag "$GIT_SHA" --message "$MSG" - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/cloudflare.md, line 103
npx --no-install wrangler versions deploy <NEW_ID>@10% <OLD_ID>@90% -y
and 10 more places
Connects to the internet
This is disclosed by the author in the skill's SKILL.md or README. Expected for a devops skill.
Found in 22 places.
Show 17 more
- plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/docker-image.md, line 38
CMD ["/nodejs/bin/node", "-e", "fetch('http://127.0.0.1:3000/healthz').then(r=>process.exit(r.ok?0:1)).catch(()=>process.exit(1))"] - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/railway.ko.md, line 105
curl -sS -o /dev/null -w '%{http_code}\n' https://<domain>/health - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/railway.ko.md, line 187
| 1 | `Application failed to respond`(502), 헬스 체크가 `service unavailable`이나 `status 400` 보고 | 앱이 `localhost`나 고정 포트에 바인드했거나 대상 포트와 수신 포트가 다름 | `0.0.0.0`에 바인드하고 ` - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/railway.ko.md, line 197
| 11 | 커스텀 도메인이 404, 인증서 오류 | CNAME만 넣고 TXT 검증 레코드가 없거나 인증서 재시도가 필요함 | 안내된 두 레코드를 그대로 넣고 `railway domain certificate retry`를 실행합니다 | `curl -I https://<domain>`가 - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/railway.md, line 105
curl -sS -o /dev/null -w '%{http_code}\n' https://<domain>/health - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/railway.md, line 187
| 1 | `Application failed to respond` (502), health check reporting `service unavailable` or `status 400` | App bound to `localhost` or a hard-coded port; targe - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/railway.md, line 197
| 11 | Custom domain returns 404, certificate error | Only the CNAME was added; the TXT verification record is missing, or the certificate needs a retry | Add b - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.ko.md, line 100
- Dokploy는 기본값이 현재 컨테이너를 멈추고 새 컨테이너를 시작하는 방식이라 배포할 때마다 Bad Gateway가 납니다. 무중단에는 Swarm 헬스체크와 업데이트 설정의 `"FailureAction": "rollback"`, `"Order": "start-first"`가 필요합 - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.ko.md, line 140
4. 프록시 경로: `kamal proxy logs`, `docker logs coolify-proxy --tail 50`, `journalctl -u caddy -n 100`, TLS와 리다이렉트 사슬을 보는 `curl -I https://<host>`입니다. - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.ko.md, line 141
5. 네트워크 내부에서: `docker exec <container> curl -fsS localhost:<port>/health`, 그다음 외부에서 `curl -fsS https://<host>/health`입니다. - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.ko.md, line 150
| 1 | 프록시가 502/503, `Connection refused`, Coolify `No available server` | 앱이 `localhost`나 `127.0.0.1`에만 바인드 | `0.0.0.0`에 바인드하고 내부 포트를 프록시와 헬스체크에 맞춤 | `docker ex - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.ko.md, line 152
| 3 | `(unhealthy)`, 헬스체크 종료 코드 `127` | 최종 이미지에 `curl`이나 `wget`이 없음 | 이미지에 하나를 설치하거나 명령 체크로 바꿈 | `docker exec <c> curl -f localhost:<port>/health; echo $?`가 0 | - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.ko.md, line 160
| 11 | ACME 챌린지 실패, `NXDOMAIN`, 인증서 미발급 | DNS가 호스트를 가리키지 않거나 80/443이 닫혔거나 전파 대기. 와일드카드에 DNS-01 누락 | A/AAAA를 바로잡고 포트를 열고 기다린 뒤 와일드카드에는 DNS-01 추가 | `dig +short A - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.md, line 100
- Dokploy stops the current container and starts the new one by default, which produces a Bad Gateway on every deploy. Zero downtime needs a Swarm health check - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.md, line 140
4. The proxy path: `kamal proxy logs`, `docker logs coolify-proxy --tail 50`, `journalctl -u caddy -n 100`, and `curl -I https://<host>` for the TLS and redirec - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.md, line 141
5. From inside the network: `docker exec <container> curl -fsS localhost:<port>/health`, then `curl -fsS https://<host>/health` from outside. - plugins/alpoxdev/hypercore/skills/hyper-deploy/references/targets/vps.md, line 150
| 1 | Proxy returns 502/503, `Connection refused`, Coolify `No available server` | App binds `localhost` or `127.0.0.1` only | Bind `0.0.0.0`, align the interna
and 2 more places
Runs commands on your computer
This is disclosed by the author in the skill's SKILL.md or README. Expected for a devops skill.
Found in 2 places.
Safer alternatives
Low-risk skills in the same category (devops) that look related. Check that one does what you need.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'hyper-deploy' ] || [ -L ~/.agents/skills/'hyper-deploy' ]; then echo 'A skill folder named hyper-deploy already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/hashgraph-online/awesome-codex-plugins' "$d" && git -C "$d" checkout --quiet '40706766fd37c03ca624f5206741fef55dd2a684' -- 'plugins/alpoxdev/hypercore/skills/hyper-deploy' && mkdir -p ~/.agents/skills && cp -R "$d"/'plugins/alpoxdev/hypercore/skills/hyper-deploy' ~/.agents/skills/'hyper-deploy' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'hyper-deploy' ~/.claude/skills/'hyper-deploy' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
The badge for hashgraph-online/awesome-codex-plugins shows the score of its lowest-scoring skill.
[](https://zalavijaysinh.github.io/skilltrust/repos/hashgraph-online/awesome-codex-plugins/)
Score history
| Date | Version | Score |
|---|
| 2026-11-11 | 4070676 | 79 |
| 2026-11-10 | f620aba | 79 |
| 2026-11-09 | 3062ea3 | 79 |
| 2026-11-08 | 057d789 | 79 |