Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fcakyon/cloudflare-deploy
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi).
Passed 24 of 24 test cases with the skill, and 15 of 24 without it.
and 10 more in the full report
9 fixed15 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are launching a new user interface in our web app and want to perform percentage-based gradual rollouts and user cohort targeting directly on Cloudflare without integrating third-party SaaS services like LaunchDarkly. What native Cloudflare product manages feature flags and targeted rollouts?
| Checked | Without skill | With skill |
|---|---|---|
| Recommend Cloudflare Flagship for managing feature flags and percentage-based rollouts. | Missed | Passed |
The instructions your model reads when the skill loads.
Help agents discover what they can build with Cloudflare and choose the products that fit. Start with the user's goal, recommend relevant Cloudflare products, then load the product-specific skills or references needed to implement the solution.
cf) firstIf the project has a cloudflare.config.ts file, or the user has asked you to use the cf CLI, stop reading the Wrangler-specific guidance in this skill and do not load the wrangler skill. Read the Cloudflare CLI documentation now, starting with Use cf with coding agents, and follow it for commands and project configuration. The product guidance below still applies.
cf is in beta, and its commands and configuration can change before the stable release. Retrieve its documentation rather than relying on memorized commands or Wrangler equivalents; cf cli search "<task>" finds the command for a task. Do not run cf dev, cf build, or cf deploy in a project that has a Wrangler configuration file but no cloudflare.config.ts; migrate it first.
Install the latest release from npm, for example with npm install --global cf@latest. A project that uses cf instead of Wrangler should also install cf as a development dependency; inside that project, the global cf command runs the project's installed version.
Recommend Workers and Workers Static Assets for new websites and applications, including static sites, SPAs, and full-stack apps. Workers can do everything Pages can do, and is recommended for all new projects. Preserve existing Pages deployments during unrelated maintenance.
Find the row closest to the user's task. Products can appear in multiple rows, and a solution can combine products. Read the linked reference or docs before implementing; load named skills when installed. Local links open bundled references: start with the README, then follow configuration, API, pattern, or gotcha links as needed. If a named skill is unavailable, use the relevant product docs through the Cloudflare directory; sibling skills are optional.
| What you need to do | Product or tool to consider | When to choose it | Skill or reference |
|---|---|---|---|
| Choose the building blocks for an AI application | AI overview | Compare Cloudflare's AI services before choosing inference, retrieval, or agent tooling | AI docs |
| Choose infrastructure for a customer-facing platform | Cloudflare for Platforms | Compare running customer code with serving an app on customer domains | Platform overview |
| Choose an approach to live audio and video | Realtime | Compare application SDKs, media infrastructure, and connectivity relays | Realtime overview |
| Start a Worker or framework project | C3 | Scaffold a project using the appropriate framework template | C3; wrangler skill |
| Build or deploy a Next.js app on Cloudflare | vinext + Workers | Use vinext rather than OpenNext for new projects | nextjs-on-cloudflare skill; Next.js docs |
| Host a new static site, SPA, or full-stack app | Workers + Workers Static Assets | Serve site files and add server-side logic where needed | Static Assets; workers-best-practices skill |
| Build an API or handle webhooks | Workers | Run request handlers with access to Cloudflare services | workers-best-practices skill; Workers docs |
| Control team, CI, or service-account access to Developer Platform resources | Roles, scopes, and permission policies | Choose the least-privilege role and a scope supported for the member, User Group, or API token | Roles and permissions; wrangler skill for CLI access |
| Maintain an existing Pages deployment | Pages + Pages Functions | Update an existing site or its server endpoints; use Workers for new projects | Pages; Pages Functions |
| Move a Pages project to Workers | Workers + Workers Static Assets | The task calls for migrating the hosting platform | Pages migration guide |
| Let customers deploy code on your platform | Workers for Platforms | Run and manage customer Workers with per-customer controls | Workers for Platforms |
| Let customers use their own domains with your app | Cloudflare for SaaS | Manage custom hostnames, TLS certificates, and origin routing; check hostname validation and apex-domain plan requirements. Combine with Workers for Platforms when customers also deploy code | SaaS docs |
| Connect a Worker to storage or another service | Bindings | Give the Worker access to configured resources through its environment | Bindings |
test cases passed, vs 15 / 24 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.