How do I install the Deploy App skill?

Run npx skillmds@latest add bex-co/deploy-app in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deploy App safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy App?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy App free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy App?

bex-co (@bex-co) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy App by bex-co — Agent Skill

Name: Deploy App
Author: bex-co

Deploy App

Deploy a bex App to the current Kubernetes cluster and verify it reaches Ready. Use when the user asks to deploy a render.yaml (or legacy bex.yml) or the sample app and validate the rollout end to end. Optional argument: path to render.yaml.

bex-co 682d99a 2 files · 2.1 KB Updated Sep 17, 2026

File contents

Deploy an App and verify it end-to-end. Use KUBECONFIG=infra/local/bex.kubeconfig if no other cluster is targeted.

Requires BEX_API_URL and BEX_API_TOKEN in the environment (scripts/app-apply.sh reads them and fails with set BEX_API_URL if unset — both are client-supplied, not in .env.example; BEX_API_PUBLIC_URL in .env.example is the unrelated backend DeployHook origin). BEX_API_TOKEN is the Hydra-issued Bearer token (API key minted via /v1/api-keys), not the removed static shared secret. Optional BEX_OWNER_ID, BEX_REPO, BEX_BRANCH narrow the deploy.

If $ARGUMENTS is a path to a render.yaml (or legacy bex.yml alias — canonical is render.yaml, see scripts/app-apply.sh), apply it with DRY_RUN=1 bash scripts/app-apply.sh $ARGUMENTS first and show the generated App CR, then bash scripts/app-apply.sh $ARGUMENTS to deploy. If $ARGUMENTS is a directory, pass the directory — the script discovers render.yaml then bex.yml inside it. Otherwise apply the sample: kubectl apply -f examples/whoami-app.yaml.
Watch until ready: poll kubectl get apps.app.bex.co <name> -o jsonpath='{.status.phase} {.status.revision} {.status.url}' until phase is Ready (timeout ~3 minutes; on timeout, show kubectl describe apps.app.bex.co <name> and the operator logs kubectl -n bex-system logs deploy/bex-controller-manager --tail=50).
If status.url is set and resolvable, curl -fsS it (use --resolve/-k only if the local mock has no real DNS/TLS) and show the response status.
Report: App name, phase, revision, url, and where the pods landed (kubectl get pods -l app.bex.co/app=<name> -o wide).

Frequently asked questions