deploy
Facilitates deployment, debugging, and teardown of VSS profiles using a structured, compose-centric workflow.
Install this skill
Security score
The deploy skill was audited on May 16, 2026 and we found 22 security issues across 4 threat categories, including 2 high-severity. Review the findings below before installing.
Categories Tested
Security Issues
Template literal with variable interpolation in command context
| 261 | The resolved YAML is saved to `<repo>/deployments/resolved.yml`. |
Template literal with variable interpolation in command context
| 265 | Unexpanded `${VAR}` tokens in `resolved.yml` mean compose did not see those env values. Diagnostic procedure and common culprits live in [`references/troubleshooting.md`](references/troubleshooting.md |
Curl to non-GitHub URL
| 349 | curl -sf http://localhost:8000/docs >/dev/null && echo "agent OK" |
Curl to non-GitHub URL
| 350 | curl -sf http://localhost:3000/ >/dev/null && echo "ui OK" |
Curl to non-GitHub URL
| 353 | curl -sf http://localhost:30082/v1/models | python3 -m json.tool |
Curl to non-GitHub URL
| 356 | curl -sf http://localhost:30081/v1/models | python3 -m json.tool |
Access to .env file
| 45 | # 1. Apply env overrides to the profile .env file |
Access to .env file
| 46 | # 2. docker compose --env-file .env config > resolved.yml (dry-run) |
Access to .env file
| 231 | **Env file location:** `<repo>/deployments/developer-workflow/dev-profile-<profile>/.env` |
Access to .env file
| 233 | > **This is the authoritative `.env`.** Every verifier, healthcheck, and |
Access to .env file
| 236 | > file** — not to `generated.env`. |
Access to .env file
| 238 | > `generated.env` is a scratchpad that `dev-profile.sh` produces during |
Access to .env file
| 241 | > deploy but leaves the base `.env` untouched will silently fail env |
Access to .env file
| 243 | > `dev-profile.sh` and see `generated.env` on disk, copy its key/value |
Access to .env file
| 244 | > lines back into the base `.env`, or re-apply your `sed` commands |
Access to .env file
| 245 | > against the base `.env` after the fact. The base `.env` is the source |
Access to .env file
| 251 | ENV_FILE=$REPO/deployments/developer-workflow/dev-profile-$PROFILE/.env |
Access to .env file
| 253 | # Read current .env, apply overrides, write back |
External URL reference
| 349 | curl -sf http://localhost:8000/docs >/dev/null && echo "agent OK" |
External URL reference
| 350 | curl -sf http://localhost:3000/ >/dev/null && echo "ui OK" |
External URL reference
| 353 | curl -sf http://localhost:30082/v1/models | python3 -m json.tool |
External URL reference
| 356 | curl -sf http://localhost:30081/v1/models | python3 -m json.tool |