wrangler
Wrangler is Cloudflare's command-line tool for building and deploying Workers across the edge platform. It handles local development, deployment, and management of Workers alongside bindings for KV storage, R2 buckets, D1 databases, Vectorize indexes, and Workers AI. The skill prioritizes current documentation over cached knowledge to ensure commands and config syntax stay accurate.
Wrangler is Cloudflare's CLI for deploying, developing, and managing Workers and related services like KV, R2, D1, and AI.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-24
Wrangler is Cloudflare's CLI for deploying, developing, and managing Workers and related services like KV, R2, D1, and AI. Wrangler is Cloudflare's command-line tool for building and deploying Workers across the edge platform. It handles local development, deployment, and management of Workers alongside bindings for KV storage, R2 buckets, D1 databases, Vectorize indexes, and Workers AI. The skill prioritizes current documentation over cached knowledge to ensure commands and config syntax stay accurate.
Use it when
- Wrangler provides `wrangler dev` to run your Worker locally with live reload, `wrangler deploy` to publish to production.
- Wrangler simplifies local setup: install it via npm, run `wrangler init` to scaffold a project.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
cloudflare/skills/wrangler · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I deploy Cloudflare Workers using wrangler?
Wrangler is Cloudflare's CLI tool for deploying Workers to the edge. After setting up your project with `wrangler init`, define your Worker code and configure bindings in `wrangler.toml`. Run `wrangler deploy` to push your Worker to Cloudflare's edge network. Wrangler handles authentication, versioning, and rollout automatically.
What are the main wrangler CLI commands for local development?
Wrangler provides `wrangler dev` to run your Worker locally with live reload, `wrangler deploy` to publish to production, and `wrangler tail` for streaming live logs. Use `wrangler secret put` and `wrangler secret delete` for managing secrets, and `wrangler kv:namespace create` for KV storage setup. Each command supports flags for environment-specific configuration.
How do I set up wrangler local development environment?
Wrangler simplifies local setup: install it via npm, run `wrangler init` to scaffold a project, then use `wrangler dev` to start a local server. Your local environment mirrors production bindings—KV namespaces, R2 buckets, D1 databases, and AI models all work locally. Configure them in `wrangler.toml` and Wrangler handles the rest.
How do I configure KV, R2, D1, and AI bindings in wrangler?
Wrangler manages bindings through `wrangler.toml`. Define KV namespaces with `[[kv_namespaces]]`, R2 buckets with `[[r2_buckets]]`, D1 databases with `[[d1_databases]]`, and AI with `[env.production.ai]`. Each binding gets a name you reference in your Worker code. Wrangler automatically injects these at runtime, both locally and on the edge.
What's the best way to manage secrets and environment variables?
Wrangler stores secrets securely using `wrangler secret put KEY` for production and `wrangler secret put KEY --env staging` for other environments. Secrets never appear in `wrangler.toml`. For non-sensitive config, use `[env.production]` variables in `wrangler.toml`. Access both via `env.VARIABLE_NAME` in your Worker code.
How do I troubleshoot wrangler startup time and binding issues?
Wrangler's `wrangler tail` streams live logs to diagnose runtime errors. For slow startup, check binding configuration in `wrangler.toml`—misconfigured namespaces or database IDs cause delays. Run `wrangler dev --debug` for verbose output. Verify credentials and environment names match your Cloudflare account settings.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Wrangler CLI
Your knowledge of Wrangler CLI flags, config fields, and subcommands may be outdated. Prefer retrieval over pre-training for any Wrangler task.
Retrieval Sources
Fetch the latest information before writing or reviewing Wrangler commands and config. Do not rely on baked-in knowledge for CLI flags, config fields, or binding shapes.
| Source | How to retrieve | Use for |
|---|---|---|
| Wrangler docs | https://developers.cloudflare.com/workers/wrangler/ |
CLI commands, flags, config reference |
| Wrangler config schema | node_modules/wrangler/config-schema.json |
Config fields, binding shapes, allowed values |
| Cloudflare docs | Search tool or https://developers.cloudflare.com/workers/ |
API reference, compatibility dates/flags |
FIRST: Check if
(truncated - see the full file via the links below)
File tree — 1 file
skills/wrangler/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Deploy and manage Cloudflare Workers using CLI commands”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Wrangler is a tool designed to help you manage and work with web development tasks more effectively. This skill introduces you to Wrangler's fundamental features and explains how it fits into modern development workflows. Gain clarity on what makes Wrangler useful and when to apply it in your projects.
Cloudflare Knowledge equips you with patterns and templates for building on the Cloudflare edge platform—Workers, Pages, R2, D1, KV, Durable Objects, and Workers AI. Reference guides cover wrangler configuration, storage service trade-offs, AI model selection, and Zero Trust setup.
Mkfast Deploy streamlines deploying mkfast-template and TanStarter projects to Cloudflare Workers by detecting which components you've enabled and generating only the steps you need. It handles template placeholder validation, environment setup, and production safety checks to prevent common deployment pitfalls.
Cloudflare Cron Triggers enables you to schedule periodic execution of Cloudflare Workers using standard cron syntax. Configure triggers in wrangler.jsonc, implement a scheduled handler in your Worker code, and test locally before deployment—all times run in UTC.
Manage ClickClack's Cloudflare Worker deployment, container lifecycle, and operational verification. Handles app rollouts, DNS routing, and health checks across product surfaces and documentation.
Wrangler Coder helps you develop and deploy Cloudflare Workers and Pages projects through the official Wrangler command-line tool. It covers project setup, configuration management across multiple environments, secrets handling, and deployment workflows. The skill also guides integration with Cloudflare's backend services including D1 databases, R2 storage, KV namespaces, and Queues.
More skills wrangler (MIT) · Cloudflare Worker (NOASSERTION) · cloudflare-workers-dev-experience (MIT) · cloudflare-pages (MIT) · cloudflare-email-service (Apache-2.0) · cloudflare-api (MIT) · vite-flare-starter (MIT) · vectorize (Apache-2.0)