{
  "skill": {
    "id": "skl_deploy_runner",
    "name": "deploy-runner",
    "plugin": "cwc-deploy",
    "description": "Executable tool that turns deploy-playbook's Desktop-Commander session-corruption guidance into tested code, not just prose. Use it whenever a deploy sequence contains a step of unknown or uncertain duration (a first-time npm install, a cold wrangler deploy, anything that might run long) — it renders a step-logging bash script, launches it backgrounded via one short call, and reads success/failure from an explicit log marker rather than session liveness. Trigger on \"deploy this and it might take a while\", \"background the deploy\", \"the session keeps dying/wedging mid-deploy\", or any deploy-playbook step where you're unsure how long a command will run. Do NOT use this for a quick, known-fast command (a `curl` verify, a one-line D1 SELECT) — deploy-playbook's plain Desktop-Commander pattern is simpler and fine there. This tool does not execute wrangler/npm/tsc itself and does not bypass any gate in gates.toml — it only generates the artifact (the script) and interprets the artifact it produces (the log); the actual commands still run through Desktop Commander or the user's own terminal, same as deploy-playbook requires.",
    "summary": "Executable tool that turns deploy-playbook's Desktop-Commander session-corruption guidance into tested code, not just prose.",
    "gated": 0,
    "source_path": "plugins/cwc-deploy/skills/deploy-runner/SKILL.md",
    "created_at": "2026-07-10 18:13:13",
    "cite_as": "https://subagentskills.com/api/skills/skl_deploy_runner"
  }
}