agentsclimarketplace

Cloudflare deploy

Skill hashorva/purrfect-harness/.agents/skills/cloudflare-deploy

Portable orchestrator/worker harness kit for AI-assisted development

Install
npx -y skills add hashorva/purrfect-harness --skill cloudflare-deploy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Deploy and verify Cloudflare Pages sites and Cloudflare Workers in this studio. MUST be used for any task involving deployment, wrangler, environment variables/secrets, CORS, custom domains, staging vs production, or "it works locally but not deployed". Also use before changing anything in wrangler.toml or Pages build settings.

SKILL.md

2.0 KB, as published. Nobody here has run it

Cloudflare deploy (Pages + Workers)

Ground rules

  • Pages: deploys are git-driven. Push to main → production; push to the staging branch → staging URL. Never deploy Pages manually when the repo is git-connected.
  • Workers: deployed via wrangler deploy from the Worker repo. A shared Worker may serve multiple products via route prefixes — check AGENTS.md before touching routing; breaking another product's prefix is a production incident.
  • Secrets live in wrangler secret (Workers) or the Pages dashboard env vars — NEVER in code, wrangler.toml plaintext, or git. Frontend gets only publishable keys (VITE_*).

Worker deploy sequence

# from the worker repo root
npx wrangler deploy --dry-run     # 1. see what would ship
npx wrangler deploy               # 2. ship
# 3. verify: curl one known-good route AND one auth-guarded route
curl -s -o /dev/null -w "%{http_code}" https://<worker-host>/<product>/<route>   # expect 401/200 as appropriate
# 4. tail if anything is off
npx wrangler tail

Change checklist for anything user-facing

  • CORS allow-list still covers: prod domain, *.pages.dev preview, localhost dev ports
  • Auth guard present on every user-scoped route (spot-check one)
  • Staging verified BEFORE main, for any change to response shapes or streaming protocols (these break clients silently)
  • Env vars/secrets referenced in code actually exist in the target environment

Escalate, don't improvise

  • DNS, custom domains, SSL settings → human
  • Deleting/renaming Worker routes → human
  • Anything in the Worker shared by multiple products where your task names only one → orchestrator

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.