wrangler

Deploy and manage Cloudflare Workers, KV, R2, and D1 via CLI.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/lirantal/vibecode-learn-english --skill wrangler-lirantal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrangler
Source: https://github.com/lirantal/vibecode-learn-english/tree/main/.cursor/skills/wrangler
Command: npx skills add https://github.com/lirantal/vibecode-learn-english --skill wrangler-lirantal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wrangling Cloudflare Workers and their related resources can be repetitive and error-prone without a unified CLI.

Core Features & Use Cases

  • Unified CLI for deploying, developing, and managing Workers, KV, R2, D1, and related services.
  • Local development & testing with quick feedback loops.
  • Production workflows including configuration, environments, and deployments across multiple resources.

Quick Start

Install Wrangler and initialize a new Worker, then run wrangler dev to start a local development server.

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 from the command line?

You can deploy and manage Cloudflare Workers using a unified CLI-driven workflow that handles configuration, environments, and deployments across multiple edge resources like KV, R2, and D1.

What is the best way to set up local development and testing for Cloudflare Workers?

The best way to set up local development for Cloudflare Workers is using a CLI tool that provides a local development server with quick feedback loops for building and testing edge applications.

Can I manage Cloudflare KV, R2, and D1 resources with a single CLI workflow?

Yes, you can manage Cloudflare KV, R2, and D1 resources using a unified CLI that simplifies deploying, developing, and managing related edge services within a single workflow.

How do I configure environment bindings for Cloudflare Workers across multiple deployments?

Configuring environment bindings for Cloudflare Workers involves using CLI config schemas that provide best-practice guidance for managing multiple environments and resource bindings during deployment.

Why does managing edge applications without a unified CLI cause deployment errors?

Managing edge applications without a unified CLI causes errors because wrangling Cloudflare Workers and related resources manually is repetitive and prone to configuration mismatches across environments.

Do I need specific configuration schemas to deploy Workers to production environments?

Yes, deploying Workers to production requires specific config schemas to manage environment bindings, multiple resources, and production workflows effectively across different deployment targets.