wrangler

Automates Cloudflare Workers configuration, local development, and deployment via wrangler CLI and wranglerc.json schema.

1|Updated Apr 6, 2025
One-click install
npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill wrangler-david-driscoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrangler
Source: https://github.com/david-driscoll/stargate-command-cluster/tree/main/.agents/skills/wrangler
Command: npx skills add https://github.com/david-driscoll/stargate-command-cluster --skill wrangler-david-driscoll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wrangler knowledge gaps and outdated CLI/config guidance make it hard to correctly build, configure, and deploy Cloudflare Workers and their related services without running into binding or type mismatches.

Core Features & Use Cases

  • Retrieval-first Wrangler accuracy: Guides you to fetch the latest Wrangler documentation and config schema instead of relying on stale memory, reducing incorrect flags and invalid fields.
  • End-to-end worker lifecycle: Covers installing Wrangler, local development, generating types, deploying (including dry runs), viewing logs, and troubleshooting common issues.
  • Comprehensive platform bindings: Helps configure and manage core integrations like KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Queues, Containers, Workflows, Pipelines, and Secrets Store for real production use cases.
  • Secure secrets handling: Emphasizes safe secret practices (no secret values in commands, logs, or hardcoded config).
  • Use case: When you need to deploy a Worker to staging and production while binding KV, R2, and AI, use this Skill to validate your config, generate correct TypeScript types, and deploy with confidence using the supported Wrangler commands.

Quick Start

Use this instruction: "Install Wrangler and scaffold a new Worker named my-worker using the latest supported approach, then deploy it to Cloudflare."

Frequently Asked Questions about wrangler

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

FAQPage Schema
How do I configure and deploy Cloudflare Workers with KV and R2 bindings?

Configure Cloudflare Workers by defining KV and R2 bindings in wrangler.jsonc with a valid compatibility_date, generate TypeScript types using wrangler types, then deploy via the Wrangler CLI for safe staging and production environments.

What is the correct way to manage Cloudflare Workers secrets across dev, staging, and production?

Managing Cloudflare Workers secrets requires applying secure workflows that avoid hardcoding values in config files or exposing them in commands and logs, utilizing the Wrangler CLI safe secret management features across dev, staging, and production environments.

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

Generate TypeScript types for Cloudflare Workers by running wrangler types after updating binding configurations in wrangler.jsonc, ensuring your TypeScript code accurately reflects KV, R2, D1, and AI integrations without type mismatches.

Does Wrangler support configuration for Cloudflare D1, Vectorize, and Queues?

Wrangler supports configuration and management for Cloudflare D1, Vectorize, Queues, Hyperdrive, Workers AI, Workflows, Pipelines, and Secrets Store, allowing comprehensive platform bindings for real production use cases within your Workers projects.

What's the best way to avoid outdated CLI flags when deploying Cloudflare Workers?

Avoid outdated Wrangler CLI flags by retrieving the latest Wrangler documentation and config schema directly from Cloudflare sources, reducing incorrect flags and invalid fields when configuring and deploying Cloudflare Workers.

Why are my Cloudflare Workers failing to deploy due to binding mismatches?

Cloudflare Workers deployment failures due to binding mismatches often stem from outdated CLI or config guidance, requiring you to validate wrangler.jsonc configurations and run wrangler types to ensure correct platform integrations before deploying.