{
  "skills": [
    {
      "id": "skl_deploy_playbook",
      "name": "deploy-playbook",
      "plugin": "cwc-deploy",
      "description": "Deploy coworker playbook — the Desktop-Commander-based workflow for scaffolding, installing, type-checking, deploying, and verifying a Cloudflare Worker from a Claude Cowork session, without poisoning the real Mac's node_modules or guessing at gotchas that already cost a prior session real time. Use when the user asks to deploy a Worker, run `wrangler deploy`, set a secret, create or migrate a D1 database, scaffold a new `workers/<name>` project, or verify a domain went live. Trigger on \"deploy this\", \"ship it\", \"wrangler deploy\", \"set the secret\", \"create a D1 database\", \"is it live\", \"scaffold a new worker\", or any Desktop-Commander `interact_with_process` session touching npm/tsc/wrangler. Do NOT use this to run npm/tsc/wrangler directly from a cloud sandbox shell — that is the one thing this playbook exists to prevent. Do NOT use for application code changes themselves (routing, HTML, SQL logic) — this is the ship step, not the build step.",
      "summary": "Deploy coworker playbook — the Desktop-Commander-based workflow for scaffolding, installing, type-checking, deploying, and verifying a Cloudflare Worker from a Claude Cowork session, without poisoning the real Mac's node_modules or guessing at gotchas that already cost a prior session real time.",
      "gated": 1,
      "source_path": "plugins/cwc-deploy/skills/deploy-playbook/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_deploy_playbook"
    },
    {
      "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"
    },
    {
      "id": "skl_edge_cache_doctor",
      "name": "edge-cache-doctor",
      "plugin": "cwc-deploy",
      "description": "Post-deploy diagnosis of the REAL stale-edge-cache-after-deploy pattern this fleet keeps hitting (subagentpython.com 2026-07-01: stale sibling content + error 1104 right after zone activation, self-resolved in seconds; subagentsystemdesigns.com 2026-07-09: first verify saw the old 725-byte parked placeholder, the retry got the 13237-byte worker body). Probes a domain N times with cache-busting queries + no-cache headers, records status/size/cf-cache-status/marker per attempt, and classifies: HEALTHY / STALE-EDGE (some attempt shows the new content — wait and re-probe before diagnosing anything) / ROUTE-MISS (consistent old content, no worker evidence — check wrangler routes, waiting won't help) / DOWN, each with its next action. Use when a just-deployed site \"still shows the old page\", a verify step failed right after wrangler deploy, curl returns a 725/1008- byte placeholder, or before filing any \"deploy didn't take\" diagnosis. Do NOT use as the pass/fail deploy gate — that is ../fleet-expansion/scripts/verify-site.sh's job (this is the diagnosis half, that is the gate half) — and do NOT use it to fix routes (route work is a deploy mutation, governed by this plugin's existing gates).",
      "summary": "Post-deploy diagnosis of the REAL stale-edge-cache-after-deploy pattern this fleet keeps hitting (subagentpython.com 2026-07-01: stale sibling content + error 1104 right after zone activation, self-resolved in seconds; subagentsystemdesigns.com 2026-07-09: first verify saw the old 725-byte parked...",
      "gated": 0,
      "source_path": "plugins/cwc-deploy/skills/edge-cache-doctor/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_edge_cache_doctor"
    },
    {
      "id": "skl_fleet_expansion",
      "name": "fleet-expansion",
      "plugin": "cwc-deploy",
      "description": "Batch-scaffold, deploy, and register MANY new Cloudflare Worker sites at once across the subagent*.com / agent*.com family, coordinated through a Postgres deploy ledger instead of conversation context. Use when launching workers for multiple owned-but-unserved domains in one pass — \"deploy workers for the domains I own\", \"launch the rest of the fleet\", \"fill the unserved zones\". Composes (never duplicates) the single-site skills: cwc-engineering:worker-build builds ONE worker, cwc-deploy:deploy-playbook/deploy-runner ship ONE worker — this skill owns only what batching adds: the typed fleet manifest, up-front accent allocation, the wave protocol with its serialization rules, the fact_fleet_deploy ledger, and batch verification. Do NOT use for a single new site (deploy-playbook alone is simpler) and do NOT let any wave edit workers/_shared/kit/ (a kit edit mid-batch is a 66-lock fleet relock event).",
      "summary": "Batch-scaffold, deploy, and register MANY new Cloudflare Worker sites at once across the subagent*.com / agent*.com family, coordinated through a Postgres deploy ledger instead of conversation context.",
      "gated": 0,
      "source_path": "plugins/cwc-deploy/skills/fleet-expansion/SKILL.md",
      "created_at": "2026-07-10 18:13:13",
      "cite_as": "https://subagentskills.com/api/skills/skl_fleet_expansion"
    }
  ]
}