wrangler

Provide retrieval-backed Wrangler CLI guidance for Cloudflare Workers deployments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of using outdated or incorrect Wrangler CLI syntax, configuration fields, and service management commands by prioritizing retrieval of the latest Cloudflare documentation over pre-trained knowledge, ensuring your Cloudflare Worker projects are configured and deployed correctly.

Core Features & Use Cases

  • Up-to-date Wrangler Guidance: Provides accurate, current instructions for all Wrangler CLI commands, flags, and configuration options for Cloudflare Workers and associated services like KV, R2, D1, Vectorize, and Queues.
  • End-to-end Workflow Support: Covers full project lifecycles from initialization and local development to deployment, secret management, version rollback, and observability.
  • Use Case: A developer building a Worker with R2 storage and D1 database bindings can use this Skill to generate a valid wrangler.jsonc configuration, run local dev with correct bindings, and deploy to production without validation errors.

Quick Start

Use the wrangler skill to configure, test, and deploy your Cloudflare Worker project with the correct Wrangler CLI commands and Cloudflare best practices.

Frequently Asked Questions about wrangler

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

FAQPage Schema
How do I configure Cloudflare Workers bindings for KV, R2, and D1 in wrangler.jsonc?

To configure Cloudflare Workers bindings for KV, R2, and D1 in wrangler.jsonc, you must define the specific binding objects under the appropriate top-level keys. This ensures your local development and production environments correctly interface with the respective Cloudflare services.

What is the correct Wrangler CLI syntax for deploying a Cloudflare Worker to production?

The correct Wrangler CLI syntax for deploying a Cloudflare Worker involves using the appropriate deploy command with valid flags for your project setup. Following current Cloudflare best practices ensures proper secret handling and version management during the production deployment lifecycle.

Does outdated Wrangler CLI knowledge cause Cloudflare Worker deployment errors?

Yes, outdated Wrangler CLI knowledge causes Cloudflare Worker deployment errors due to deprecated configuration fields and invalid command flags. Retrieving up-to-date guidance for the current Wrangler configuration schema prevents these validation errors and ensures successful project initialization and management.

Can I run local development for Cloudflare Workers with Vectorize and Queues bindings?

Yes, you can run local development for Cloudflare Workers with Vectorize and Queues bindings by specifying the correct service bindings in your configuration file. This allows you to test interactions with these associated Cloudflare services locally before deploying to production.

What's the best way to manage secrets and observability for a Cloudflare Worker project?

The best way to manage secrets and observability for a Cloudflare Worker project is by using the valid Wrangler CLI commands dedicated to secret handling and logging. Adhering to Cloudflare best practices ensures secure secret exposure and effective lifecycle management during local development and deployment.