agentleFS
Sign inStart free
metaspartanmetaspartan/cybara/skills/cloudflare-temporary-deploy/SKILL.md

cloudflare-temporary-deploy

Skill38 starsChanged 5 months agoMITView on GitHub

Deploy a temporary Cloudflare Workers preview with Wrangler for short-lived web app smoke tests.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when the user wants a short-lived public smoke-test URL for a Worker or static web app without setting up a permanent Cloudflare …

    line 9
  2. Very specific:

    No Cloudflare credentials in the shell when using --temporary.

    line 16
  3. Distinctive:

    Treat the claim URL as credential-equivalent.

    line 18
  4. Distinctive:

    Verify the live URL:

    line 40
  5. Very specific:

    Always verify the live URL with curl.

    line 48
  6. Very specific:

    If the shell is authenticated, --temporary may fail by design.

    line 49
  7. Distinctive:

    Do not put secrets into Worker source, Wrangler config, or deploy logs.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloudflare Temporary Deploy

Use this when the user wants a short-lived public smoke-test URL for a Worker or static web app without setting up a permanent Cloudflare project.

Cybara repos use Bun. Translate npm/npx examples to bunx.

Preconditions

  • Node-compatible project or Worker entrypoint.
  • No Cloudflare credentials in the shell when using --temporary.
  • Temporary deployments expire unless claimed.
  • Treat the claim URL as credential-equivalent.

Commands

Check Wrangler:

bunx wrangler@latest --version

Deploy:

bunx wrangler@latest deploy --temporary

Capture output to parse URLs:

bunx wrangler@latest deploy --temporary 2>&1 | tee /tmp/wrangler-temporary-deploy.log

Verify the live URL:

curl -sS "<live_url>"

Rules

  • Always verify the live URL with curl; do not trust deploy output alone.
  • If the shell is authenticated, --temporary may fail by design. Ask before logging out or unsetting credentials.
  • Do not put secrets into Worker source, Wrangler config, or deploy logs.
  • For anything longer-lived than a demo/smoke test, use a real Cloudflare account and configured project.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free