Agent skill

Cloudflare Temporary Deploy

by Luciole-Studio in Luciole-Studio/Misaka-Agent

Deploy a Worker live, no account, via wrangler --temporary. An agent skill from Luciole-Studio/Misaka-Agent.

MITAuto-check passedDevOps & Cloud

Install Cloudflare Temporary Deploy

skills CLI
$ npx skills add Luciole-Studio/Misaka-Agent --skill cloudflare-temporary-deploy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Luciole-Studio/Misaka-Agent cloudflare-temporary-deploy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Luciole-Studio/Misaka-Agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/misaka/core/skills/assets/optional/web-development/cloudflare-temporary-deploy .claude/skills/cloudflare-temporary-deploy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cloudflare-temporary-deploy
GitHub stars
125
Used in
2 other repos
Token cost
~1.9k tokens
SKILL.md length
901 words
Files
2 (incl. scripts)
Skills in repo
76
Repo updated
First seen
Licence
MIT

At a glance

Deploy a Worker live, no account, via wrangler --temporary. An agent skill from Luciole-Studio/Misaka-Agent.

  • Works in 6 steps: Scaffold a minimal Worker (skip if the… → Deploy with --temporary from the project… → Parse the URLs from that output. Run the… → …
  • Tasks that involve Deployment
  • SKILL.md covers When to Use, When NOT to Use, Prerequisites and How to Run, plus 3 more sections
  • Runs Python scripts from its folder; calls npx, wrangler and python; needs CLOUDFLARE_API_TOKEN and CLOUDFLARE_API_KEY

What it does

Cloudflare Temporary Deploy is an agent skill from Luciole-Studio/Misaka-Agent. Deploy a Worker live, no account, via wrangler --temporary.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/parse_deploy_output.py`).

It sits in DevOps & Cloud, covering Deployment. It works with Cloudflare and Cloudflare Workers. The repository describes itself as: A multi-agent research system for the humanities and social sciences. The licence is MIT.

When your agent uses it

  • Tasks that involve Deployment

Example prompts

  • “/cloudflare-temporary-deploy”

Requirements

  • Python 3
  • Node.js
  • A credential in CLOUDFLARE_API_TOKEN
  • A credential in CLOUDFLARE_API_KEY

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Scaffold a minimal Worker (skip if the project already exists). A Worker needs a wrangler.toml (or wrangler.jsonc) and an entry script…
  2. Deploy with --temporary from the project directory
  3. Parse the URLs from that output. Run the helper to extract them reliably instead of eyeballing
  4. Verify the deploy is actually live — do not trust the deploy log alone. curl the live URL and confirm the body matches what the code returns
  5. Iterate. Edit the code, redeploy with the same npx wrangler@latest deploy --temporary. Within the 60-minute window Wrangler reuses the…
  6. Hand the claim URL to the user. Tell them: open it within 60 minutes to keep the deployment and any resources; if they don't claim it…

What it can do on your machine

Read from SKILL.md and the folder at commit 77871d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • npx
    • wrangler
    • python
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, wrangler and curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • CLOUDFLARE_API_TOKEN
    • CLOUDFLARE_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cloudflare Temporary Deploy loads about 1.9k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 901 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from Luciole-Studio/Misaka-Agent at commit 77871d7, republished under its MIT licence (© Luciole-Studio). 901 words, ~1,859 tokens.

Download SKILL.mdSave it as .claude/skills/cloudflare-temporary-deploy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
cloudflare-temporary-deploy
description
Deploy a Worker live, no account, via wrangler --temporary.
version
1.0.0
author
Hermes Agent
license
MIT
platforms
linux, macos, windows

Cloudflare Temporary Deploy Skill

Deploy a Cloudflare Worker to a live workers.dev URL with zero account setup, using wrangler deploy --temporary. Cloudflare provisions a throwaway account, deploys, and prints a claim URL valid for 60 minutes; unclaimed accounts auto-delete. This gives an agent a tight write → deploy → verify loop without any OAuth, signup, or token copy-paste.

This skill does NOT cover production deploys (use wrangler login + a permanent account for those), nor non-Worker Cloudflare products beyond the temporary-account limits below.

When to Use

Load this skill when the user wants to:

  • Ship agent-written code to a live URL without first creating a Cloudflare account — "deploy this and give me a link"
  • Iterate in a background/autonomous session where a browser OAuth step would be a hard stop
  • Prototype or evaluate Workers quickly with a throwaway, claimable target
  • Build a self-verifying deploy loop — deploy, curl the live URL, confirm output matches the code, redeploy

When NOT to Use

  • Production or CI/CD → use a permanent account (wrangler login or CLOUDFLARE_API_TOKEN). --temporary errors out if any credential is present.
  • Wrangler is already authenticated → --temporary returns an error by design. Run wrangler logout first only if the user explicitly wants a throwaway deploy.
  • Long-lived hosting → temporary deployments are deleted after 60 minutes unless claimed.

Prerequisites

  • Wrangler 4.102.0 or later. This is the version that introduced --temporary. Earlier versions do not have it. Verify with npx wrangler@latest --version.
  • Node 18+ / npm (or npx, yarn, pnpm). No global install needed — npx wrangler@latest works.
  • No Cloudflare credentials present. --temporary only works when Wrangler is unauthenticated: no OAuth login, no CLOUDFLARE_API_TOKEN / CLOUDFLARE_API_KEY env var, no ~/.wrangler / ~/.config/.wrangler cached OAuth. Use the terminal tool's environment as-is; do not set those vars.
  • Network egress to cloudflare.com and workers.dev.
  • Using --temporary accepts Cloudflare's Terms of Service and Privacy Policy.

How to Run

Use the terminal tool for every step. Always pin the version (wrangler@latest or wrangler@4.102.0 or newer) so you don't accidentally run an old global wrangler that lacks the flag.

  1. Scaffold a minimal Worker (skip if the project already exists). A Worker needs a wrangler.toml (or wrangler.jsonc) and an entry script. Minimal TypeScript example — write these with write_file:

    wrangler.jsonc:

    jsonc
    {
      "name": "hello-agent",
      "main": "src/index.ts",
      "compatibility_date": "2025-01-01"
    }

    src/index.ts:

    typescript
    export default {
      async fetch(): Promise<Response> {
        return new Response("hello cloudflare");
      },
    };
  2. Deploy with --temporary from the project directory:

    npx wrangler@latest deploy --temporary

    The proof-of-work check adds a short automatic delay. On success Wrangler prints an Account: <name> (created) (or (reused)) line, a Claim URL, and the live https://<worker>.<account>.workers.dev URL.

  3. Parse the URLs from that output. Run the helper to extract them reliably instead of eyeballing:

    npx wrangler@latest deploy --temporary 2>&1 | python scripts/parse_deploy_output.py

    (Resolve scripts/parse_deploy_output.py to this skill's absolute path.) It prints JSON: {"live_url", "claim_url", "account", "account_state", "expires_minutes", "deployed"}.

  4. Verify the deploy is actually live — do not trust the deploy log alone. curl the live URL and confirm the body matches what the code returns:

    curl -sS <live_url>
  5. Iterate. Edit the code, redeploy with the same npx wrangler@latest deploy --temporary. Within the 60-minute window Wrangler reuses the cached temporary account (Account: <name> (reused)), so the URL stays stable. curl again to confirm the change.

  6. Hand the claim URL to the user. Tell them: open it within 60 minutes to keep the deployment and any resources; if they don't claim it, everything auto-deletes. Treat the claim URL as a secret — it grants ownership of the account.

Show full SKILL.md (367 more words)Show less

Quick Reference

StepCommand
Check version (need 4.102.0+)npx wrangler@latest --version
Deploy (no account)npx wrangler@latest deploy --temporary
Deploy + parse URLsnpx wrangler@latest deploy --temporary 2>&1 | python scripts/parse_deploy_output.py
Verify livecurl -sS <live_url>
Clear cached temp accountnpx wrangler@latest logout
Temporary account product limits
ProductLimit on a temporary account
WorkersDeploys to workers.dev
Static AssetsUp to 1,000 files, 5 MiB each
KVAllowed
D11 database, 100 MB per DB / 100 MB total
Durable ObjectsAllowed
Hyperdrive2 configs, 10 connections
QueuesUp to 10
SSL/TLS certsAllowed

Pitfalls

  • --temporary is not in wrangler deploy --help and is not a global flag. It is intentionally hidden and surfaced dynamically: when an unauthenticated wrangler deploy fails, Wrangler prints "rerun with --temporary". Don't conclude the flag is missing just because --help omits it — check the version instead.
  • Old global wrangler. A stale globally-installed wrangler (< 4.102.0) silently lacks the flag. Always invoke npx wrangler@latest (or a pinned >=4.102.0) so you control the version.
  • Auth present → hard error. If wrangler login was ever run, or CLOUDFLARE_API_TOKEN/CLOUDFLARE_API_KEY is set, --temporary errors. Either unset the var for this shell or wrangler logout. Never strip a user's real credentials without telling them.
  • Rate limiting. Creating temporary accounts too fast fails. Reuse the cached account (just redeploy) within the 60-minute window instead of forcing a new one; if rate-limited, wait or use a permanent account.
  • 60-minute hard expiry, not extendable. If the deploy must outlive an hour, the user must claim it. Surface this clearly.
  • curl may briefly serve the old body after a redeploy. workers.dev has a short edge cache; the (reused) line plus a new Current Version ID confirm the deploy succeeded even if curl shows stale content for a few seconds. Re-curl, or add a cache-busting query string, before concluding a redeploy failed.
  • Don't log the claim URL into shared transcripts as "just a link." It is credential-equivalent.

Verification

  • npx wrangler@latest --version returns >= 4.102.0.
  • npx wrangler@latest deploy --temporary prints a workers.dev live URL and a claim-preview?claimToken= claim URL.
  • curl -sS <live_url> returns the exact body the Worker code produces.
  • A second deploy reports Account: <name> (reused) and the live URL is unchanged.
  • The parser script's self-test passes: python scripts/parse_deploy_output.py --selftest.

© Luciole-Studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in misaka/core/skills/assets/optional/web-development/cloudflare-temporary-deploy of Luciole-Studio/Misaka-Agent.

  • SKILL.md
  • scripts/parse_deploy_output.py

Open the folder on GitHubat commit 77871d7

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in Luciole-Studio/Misaka-Agent, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Cloudflare Temporary Deploy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cloudflare Temporary Deploy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cloudflare Temporary Deploy this skillLuciole-Studio/Misaka-Agent1252 repos~1.9kAutomated safety check: PassMIT
Nextjs On Cloudflarecloudflare/skills3k2 repos~678Automated safety check: PassApache-2.0
Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template786—~5.9kAutomated safety check: NotesMIT
Lunora Deployanolilab/lunora283—~2.1kAutomated safety check: PassCustom licence
Deploy Microfeedmicrofeed/microfeed4.1k—~6.6kAutomated safety check: PassAGPL-3.0
Wranglercloudflare/skills3k2 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Nextjs On Cloudflare

    cloudflare/skills

    Official

    Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext.

    3k GitHub starsUsed in 2 repos~678 tokens
    DevOps & CloudAuto-check passed
  • Prepare Cloudflare Production Deployment

    LubomirGeorgiev/cloudflare-workers-nextjs-saas-template

    Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.

    786 GitHub stars~5.9k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Lunora Deploy

    anolilab/lunora

    Deploys a Lunora app to Cloudflare. An agent skill from anolilab/lunora.

    283 GitHub stars~2.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Deploy Microfeed

    microfeed/microfeed

    Deploy and administer microfeed through the source-code-free @microfeed/cli launcher or the project-owned yarn manage CLI.

    4.1k GitHub stars~6.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Wrangler

    cloudflare/skills

    Official

    Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, Previews, deployment, and Cloudflare resource management.

    3k GitHub starsUsed in 2 repos~2.8k tokens
    DevOps & CloudAuto-check passed
  • Cloudflare Deploy

    JetBrains/skills

    Official

    Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services.

    363 GitHub starsUsed in 6 repos~1.8k tokens
    DevOps & CloudAuto-check passed

More from Luciole-Studio/Misaka-Agent

All 76 skills in this repo
  • Kanban Video Orchestrator

    Luciole-Studio/Misaka-Agent

    Plan and run multi-agent video production pipelines. An agent skill from Luciole-Studio/Misaka-Agent.

    125 GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check: notes
  • Ast Grep

    Luciole-Studio/Misaka-Agent

    AST-aware structural code search and rewrite via ast-grep. An agent skill from Luciole-Studio/Misaka-Agent.

    125 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Drug Discovery

    Luciole-Studio/Misaka-Agent

    Drug discovery: ChEMBL search, drug-likeness, interactions. An agent skill from Luciole-Studio/Misaka-Agent.

    125 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Fitness Nutrition

    Luciole-Studio/Misaka-Agent

    Workout planning, macros, and body metrics via wger/USDA. An agent skill from Luciole-Studio/Misaka-Agent.

    125 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed
  • Hyperframes

    Luciole-Studio/Misaka-Agent

    Render MP4/WebM videos from HTML compositions. An agent skill from Luciole-Studio/Misaka-Agent.

    125 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Osint Investigation

    Luciole-Studio/Misaka-Agent

    Follow the money via public records and sanctions data. An agent skill from Luciole-Studio/Misaka-Agent.

    125 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed

Categories

Questions about Cloudflare Temporary Deploy

What does Cloudflare Temporary Deploy do?

Deploy a Worker live, no account, via wrangler --temporary. An agent skill from Luciole-Studio/Misaka-Agent. Cloudflare Temporary Deploy is an agent skill from Luciole-Studio/Misaka-Agent. Deploy a Worker live, no account, via wrangler --temporary.

When should I use Cloudflare Temporary Deploy?

Cloudflare Temporary Deploy fits situations like: tasks that involve Deployment.

How do I install Cloudflare Temporary Deploy in Claude Code?

Run `npx skills add Luciole-Studio/Misaka-Agent --skill cloudflare-temporary-deploy -a claude-code`. Or copy the skill folder (misaka/core/skills/assets/optional/web-development/cloudflare-temporary-deploy in Luciole-Studio/Misaka-Agent) into .claude/skills/cloudflare-temporary-deploy in your project. Claude Code loads it when a task matches its description.

How do I install Cloudflare Temporary Deploy in Codex?

Run `npx skills add Luciole-Studio/Misaka-Agent --skill cloudflare-temporary-deploy -a codex`. Or copy the skill folder (misaka/core/skills/assets/optional/web-development/cloudflare-temporary-deploy in Luciole-Studio/Misaka-Agent) into .agents/skills/cloudflare-temporary-deploy in your project. Codex loads it when a task matches its description.

Can I use Cloudflare Temporary Deploy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Luciole-Studio/Misaka-Agent --skill cloudflare-temporary-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cloudflare-temporary-deploy, .gemini/skills/cloudflare-temporary-deploy, .github/skills/cloudflare-temporary-deploy and .opencode/skills/cloudflare-temporary-deploy in your project.

What does Cloudflare Temporary Deploy need to run?

Going by SKILL.md and its folder, Cloudflare Temporary Deploy needs Python for the scripts in its folder, the command-line tools its instructions call (npx, wrangler, python and curl) and credentials named CLOUDFLARE_API_TOKEN and CLOUDFLARE_API_KEY. Our summary lists: Python 3; Node.js; A credential in CLOUDFLARE_API_TOKEN; A credential in CLOUDFLARE_API_KEY.

Does Cloudflare Temporary Deploy access the network?

SKILL.md contains no URLs. Its commands use npx and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cloudflare Temporary Deploy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Cloudflare Temporary Deploy use?

Cloudflare Temporary Deploy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cloudflare Temporary Deploy use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cloudflare Temporary Deploy?

Skills that share tags, products or a category with Cloudflare Temporary Deploy: Nextjs On Cloudflare (cloudflare/skills, 3k stars), Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars), Lunora Deploy (anolilab/lunora, 283 stars) and Deploy Microfeed (microfeed/microfeed, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cloudflare Temporary Deploy?

Luciole-Studio (a GitHub organization) maintains it in Luciole-Studio/Misaka-Agent, which has 125 GitHub stars. The repository holds 76 skills in this directory. The repository was last updated on October 7, 2026.

Source: Luciole-Studio/Misaka-Agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.