wrangler

Automate Cloudflare Workers deployment and management with the Wrangler CLI.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cenjie/skills --skill wrangler-cenjie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrangler
Source: https://github.com/cenjie/skills/tree/main/skills/wrangler
Command: npx skills add https://github.com/cenjie/skills --skill wrangler-cenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps Wrangler CLI usage, configuration, and deployment practices current to avoid runtime errors, binding mismatches, and insecure secret handling when developing and operating Cloudflare Workers.

Core Features & Use Cases

  • Up-to-date CLI guidance: Prefer retrieval from Cloudflare docs for the latest flags, subcommands, and config schema to avoid using stale pre-trained knowledge.
  • Configuration best practices: Use wrangler.jsonc, maintain a recent compatibility_date, and generate TypeScript types after config changes to prevent binding and type mismatches.
  • Local and remote workflows: Run local development with simulated bindings or enable remote bindings for integration testing; manage KV, R2, D1, Durable Objects, Workers AI, Vectorize, Hyperdrive, Containers, Queues, Workflows, Pipelines, Pages, and Secrets Store.
  • Operational tooling: Tail logs, profile startup, manage versions and rollbacks, handle migrations and secrets securely, and integrate wrangler types into CI for validation.
  • Use Case: Prepare a production deployment by defining env.staging and env.production, setting remote bindings for AI and Vectorize as needed, running types generation in CI, and performing a dry-run deploy before production rollout.

Quick Start

Initialize a new Cloudflare Worker project, set a recent compatibility_date in wrangler.jsonc, add required bindings (for example AI and R2), run wrangler types to generate types, and then deploy to staging for verification.

Frequently Asked Questions about wrangler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy and manage Cloudflare Workers using the Wrangler CLI?

To deploy and manage Cloudflare Workers, use the Wrangler CLI to automate local development, configure wrangler.jsonc with a recent compatibility_date, define bindings, and execute staging and production deployments securely.

How do I configure local and remote bindings for Cloudflare Workers development?

Configure local and remote bindings for Cloudflare Workers by defining resources like KV, R2, D1, and AI in wrangler.jsonc, enabling simulated local bindings or remote bindings for integration testing during development.

What is the best way to handle secrets in a Cloudflare Workers deployment?

The best way to handle secrets in a Cloudflare Workers deployment is to use the Wrangler CLI to securely manage and inject secrets, preventing insecure secret handling and runtime errors in staging and production workflows.

How do I generate TypeScript types after changing Cloudflare Workers configuration?

Generate TypeScript types after changing Cloudflare Workers configuration by running the wrangler types command to prevent binding and type mismatches, ensuring your wrangler.jsonc schema stays current.

Can I run a dry-run deploy before rolling out Cloudflare Workers to production?

Yes, you can run a dry-run deploy before rolling out Cloudflare Workers to production by defining env.staging and env.production configurations and validating your setup through the Wrangler CLI.

Why does my Cloudflare Workers deployment fail with binding mismatches?

Cloudflare Workers deployments fail with binding mismatches when wrangler.jsonc lacks a recent compatibility_date or up-to-date configuration, requiring Wrangler CLI retrieval from Cloudflare docs to ensure correct schema usage.