- Home
- Skills
- APIs & Backend
- cloudflare-deploy
Cloudflare Deploy
Set up and diagnose Cloudflare Pages, Workers, DNS, Email Routing and D1, and fix deploys that serve errors or stale content.
$15
Works with the AI Agents you already use
cloudflare-deploy
Example session with this skill installed
I need to deploy my site to Cloudflare Pages and update the Worker. The Worker uses a D1 database named 'users_db'. Use branch main and project 'my-web-app'.
- Read your context and instructions
- Compiled the cloudflare-deploy
I have prepared and executed the deployment for 'my-web-app'. I verified the compatibility dates and ensured the D1 binding for users_db was included in the metadata to prevent it from being wiped.
Deployment Results
| Component | Action | Status | Details |
|---|---|---|---|
| Pages | wrangler pages deploy | ✅ Success | Deployed to main branch |
| Worker | wrangler deploy | ✅ Success | Bindings preserved: users_db (D1) |
| Assets | Cache-bust Check | ✅ Passed | All .js/.css files versioned |
| Live Check | HTTP GET | ✅ 200 OK | Verified on production domain |
Configuration Applied
# wrangler.toml snippet used for deploy
name = "my-web-app-worker"
main = "src/index.ts"
compatibility_date = "2024-11-01"
[[d1_databases]]
binding = "users_db"
database_name = "users_db"
database_id = "00000000-0000-0000-0000-000000000000"
Next steps
- Visit the production URL and hard-refresh to confirm the new logic is active.
- Check the Cloudflare Dashboard under Workers > Settings > Bindings to confirm
users_dbis still listed. - If you see a 500 error, run the redeploy command specifically through the Wrangler CLI as per Rule 1.
Connects securely to your tools. The creator never sees your data.
About this skill
Deploying to Cloudflare often fails due to silent configuration wipes or browser caching issues that waste hours of debugging. This skill enforces a strict, battle-tested deployment protocol for Cloudflare Pages, Workers, DNS, and D1 to ensure every release is functional and persistent.
What it does
- Automated Deployments executes Cloudflare Pages and Worker deploys using Wrangler with mandatory binding persistence.
- Cache Management forces version query string bumps on all JavaScript and CSS assets to prevent stale content delivery.
- Config Validation compares compatibility dates between local files and deployment tools to prevent runtime drift.
- Infrastructure Setup configures DNS records, Email Routing, and D1 databases in the correct dependency order.
- Error Diagnosis maps specific deployment symptoms to proven fixes using an internal error-diagnosis guide.
How it works
- Initialize the project by loading checklists for DNS, Pages, and Workers from the reference files.
- Pre-deploy Check runs the
deploy-check.pyscript to scan for unversioned assets and verify current Worker bindings. - Execution runs the deployment command, passing the full list of D1, KV, and R2 bindings to prevent metadata wipes.
- Verification performs a live check of the homepage and sub-pages to confirm 200 OK status and content freshness.
Frameworks & tools
Cloudflare Pages, Cloudflare Workers, Wrangler CLI, D1 Database, KV, R2, Python 3, and DNS/Email Routing.
Why this beats prompting it yourself
Standard prompts often forget that Cloudflare Worker redeploys wipe any bindings not explicitly passed in the command. This skill treats every deployment rule as a "scar" from a real project failure, ensuring you never lose a database connection or serve a 500 error due to direct-upload bugs.
Use cases
- Deploying a static site with an API Worker while preserving all D1 and KV bindings.
- Troubleshooting a "live" site that is serving 500 errors or outdated code after a successful build.
- Setting up a new production domain with DNS, Email Routing, and cron triggers from scratch.
- Adding secrets and environment variables to a Worker without breaking existing routes.
Known limitations
Does not support concurrent builds or deploys against the same folder. Cloudflare Free plan limits apply, such as the 5 cron trigger maximum. Outbound port 25 is blocked by the platform.
No concurrent builds/deploys on one folder. Free plan caps at 5 crons. Port 25 is blocked. Browser screenshot tools may fail if Bot Fight Mode is active.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed today
Requires
Permissions
Allowed Hosts