Cloudflare Drop deploys small static sites to temporary Cloudflare Workers previews with private claim delivery and strict consent controls.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install cloudflare-drop
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install cloudflare-drop using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Cloudflare Drop?
Cloudflare Drop is an Openclaw Skills workflow for safely publishing small, non-sensitive static sites to short-lived Cloudflare Workers preview URLs. It is designed for cases where an intended user explicitly accepts the Cloudflare Terms and Privacy Policy and needs a temporary workers.dev link that can be claimed privately.
This skill emphasizes controlled deployment, privacy-preserving link delivery, and strict boundary enforcement. Openclaw Skills uses it to ensure only eligible static content is published, claim URLs stay private, and deployments halt immediately when consent, validation, or file-safety checks fail.
Cloudflare Drop Use Cases
- Deploying a small static website to a temporary
workers.devpreview URL. - Sharing a private claim link with a specific intended user after explicit consent.
- Publishing a simple site that contains a root
index.htmland no sensitive assets. - Creating short-lived demo or proof-of-concept deployments for review.
- Diagnosing failed Cloudflare preview deployments within the skill's supported limits.
- Using Openclaw Skills to standardize safe, repeatable Cloudflare Workers previews.
How Cloudflare Drop Works
- Present the Cloudflare Terms and Privacy Policy to the intended user and verify explicit acceptance.
- Validate that the site is a small, non-sensitive static directory with a root
index.htmland no disallowed files. - Create a new private Claim URL file path and ensure it is protected with
0600permissions and not overwritten. - Run the deployment script with the static directory, the
--accept-termsflag, and the private claim file path. - Retrieve the Live URL for the deployed Workers preview.
- Read the Claim URL from the private file and deliver it only to the intended user.
- If consent, input validation, or claim-file creation fails, stop immediately rather than provisioning the deployment.
- For API failures or limit checks, consult the Cloudflare API reference before retrying or expanding scope.
Cloudflare Drop Setup
- Ensure Node.js is available in the environment.
- Confirm the static site is eligible: regular files only, a root
index.html, and no private content, symlinks, or large media bundles. - Prepare a brand-new private file path for the Claim URL.
- Obtain explicit acceptance of the Cloudflare Terms and Privacy Policy from the intended user.
- Deploy with the provided script:
node <installed-skill-dir>/scripts/deploy.mjs <static-directory> \
--accept-terms \
--claim-url-file <new-private-file>
- Verify the script creates the claim file with
0600permissions and does not overwrite an existing file. - After a successful run, share the Live URL broadly only as appropriate and deliver the Claim URL exclusively to the intended user.
- If diagnosing failures, read
references/cloudflare-api.mdbefore retrying or adjusting deployment scope.
Cloudflare Drop Data Schema & Taxonomy
Deployment inputs
| Field | Type | Notes |
|---|---|---|
static-directory |
directory path | Source directory for the site to deploy |
--accept-terms |
flag | Required confirmation that Cloudflare Terms and Privacy Policy were accepted |
--claim-url-file |
file path | New private path for the Claim URL; must not already exist |
Output artifacts
| Artifact | Purpose | Visibility |
|---|---|---|
| Live URL | Temporary Cloudflare Workers preview URL | Can be shared as the deployment result |
| Claim URL file | Stores the private claim link | Private only, created with 0600 permissions |
Content taxonomy and limits
- Allowed content:
- Regular static files
- Root
index.html
- Disallowed content:
- Private files
- Symlinks
- Large media bundles
- Operational metadata:
- Consent status must be explicit before deployment
- Claim URL handling must remain private
- Failure states should stop provisioning immediately
Reference dependency
references/cloudflare-api.md: used for troubleshooting API failures, retry decisions, and boundary checks on whether a site exceeds the skill's supported limits.
Cloudflare Drop Advanced Features
- Enforces explicit user consent before any deployment action begins.
- Creates the Claim URL file with restrictive
0600permissions to protect private delivery. - Refuses to overwrite an existing Claim URL file, reducing accidental link exposure.
- Applies strict deployment boundaries to keep Openclaw Skills focused on safe, small static sites only.
- Provides a deterministic CLI workflow for repeatable Cloudflare Workers preview deploys.
- Includes a reference-driven troubleshooting path for API failures and scope validation.
SKILL.md
Loading
Related Openclaw Skills
News Impact Scale
News Impact Scale turns any article URL into a personalized prev/current/future impact analysis grounded in historical benchmarks and your own context.
Dice Roller
A CLI-based dice roller for tabletop-style notation, reproducible random rolls, and RPG check resolution.
Credential Exposure Map
Credential Exposure Map helps OpenClaw Skills discover, classify, and risk-score every credential an agent can access.
Asset Intake Checklist
Asset Intake Checklist helps you register, normalize, and verify new resources in a shared library with consistent metadata and follow-up handling.
Tailor Resume
Openclaw Skills Tailor Resume updates an existing Google Docs resume for a specific job while staying strictly truthful and evidence-based.
Editor in Chief
Editor in Chief is an Openclaw Skills editorial agent for correcting prose while preserving the writer’s voice, tone, and intent.
Featured*
