Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fcakyon/wrangler
Run or troubleshoot Wrangler CLI commands and configure Worker projects for local development, deployment, and Cloudflare resource management.
Passed 17 of 22 test cases with the skill, and 6 of 22 without it.
and 14 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are running Workers Previews for a Worker that uses a staging environment configured under `[env.staging]`. What command flag must we pass to preview commands when interacting with this staging environment?
| Checked | Without skill | With skill |
|---|---|---|
| Instructs passing the --env flag consistently to all Preview commands targeting specific Wrangler environments. | Passed | Passed |
| Notes that omitting --env will default preview commands to the top-level Worker configuration. | Missed | Passed |
The instructions your model reads when the skill loads.
If the project has a cloudflare.config.ts file, or the user has asked you to use the cf CLI, do not use this skill. Follow the Cloudflare CLI documentation instead.
Use the project's Wrangler version and retrieve the relevant documentation before writing commands or configuration. CLI flags and configuration fields change; do not rely on memorized examples.
Use the Cloudflare MCP docs tool if available, or fetch the relevant linked page directly. Follow links to the specific command or product involved; avoid loading the entire reference. If a page moves, rediscover it through the Wrangler command index or Cloudflare docs search.
| Task | Source |
|---|---|
| Discover commands and flags, including resource management, deployments, rollback, and diagnostics | Project-local wrangler --help and wrangler <command> --help; command reference |
| Edit config or add a binding | Installed wrangler/config-schema.json (usually under node_modules); configuration reference |
| Deploy a framework application | Framework guides; follow the guide for the project's existing framework and adapter |
| Migrate an application to Workers when requested | Pages to Workers; Vercel to Workers |
| Configure staging or production | Environments |
| Set secrets locally, in CI, or on a deployed Worker | Secrets |
| Generate binding and runtime types | TypeScript |
| Run locally or choose a testing approach | Local development; testing |
| Choose roles, scopes, or API token permissions for Wrangler | Roles and permissions; Workers roles and permissions |
| Create or manage a branch or pull request environment | Previews overview; get started; configuration |
| Decide whether Preview resources are isolated or shared | Resources and isolation, including its current limitations |
| Configure Preview URLs, access, debugging, or CI | Custom domains; test and debug; examples |
| Choose between Previews, Version URLs, and Wrangler environments | Compare workflows |
| Diagnose authentication or select an account | General commands, including whoami; authentication profiles |
| Deploy an unauthenticated prototype | Claim deployments for eligibility, expiry, and claim URL handling; use a permanent account for production or CI |
Use installed help and schema to check whether documented features exist in the project's version. If a required feature needs an upgrade, make that dependency explicit. If retrieval is unavailable, state the gap and use available local evidence rather than inventing syntax.
wrangler.jsonc for new config. Set a new project's compatibility date to today; review runtime changes and test when advancing an existing project's date. Preserve existing project conventions and avoid incidental format migrations.test cases passed, vs 6 / 22 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.