Deploy and manage Cloudflare Workers, KV, R2, D1, and other bindings using Wrangler CLI commands.
npx skills add https://github.com/lettucebo/Skills --skill wrangler-lettucebo
Please help me install this Agent Skill. Skill: wrangler Source: https://github.com/lettucebo/Skills/tree/main/skills/cloudflare/wrangler Command: npx skills add https://github.com/lettucebo/Skills --skill wrangler-lettucebo
wrangler dev with local or remote bindings, deploy with environments, dry runs, and version rollbacks. - Resource Management: Create and manage KV namespaces, R2 buckets, D1 databases, Vectorize indexes, Hyperdrive configs, Queues, Containers, Workflows, Pipelines, and Secrets Store. - Configuration & Types: Author wrangler.jsonc configs with bindings and generate TypeScript types via wrangler types. - Use Case: You need to deploy a Worker with a D1 database and R2 bucket. The skill retrieves the latest Wrangler docs, writes a correct wrangler.jsonc with bindings, runs migrations, and deploys with a dry-run validation first. ## Quick Start Ask the AI to create a new Cloudflare Worker with a D1 database binding and deploy it using Wrangler.High-intent search queries and answers about installing and using this skill.
Run `wrangler deploy` after configuring `wrangler.jsonc` with your Worker name, entry point, and compatibility date. Use `wrangler deploy --dry-run` to validate first, and `wrangler deploy --env staging` to target a specific environment.
Run `wrangler dev` to start a local dev server with simulated bindings. Set `remote: true` on specific bindings in your config to connect to real resources like Workers AI or Vectorize while running locally.
Prefer `wrangler.jsonc` because newer Wrangler features are JSON-only. Add the `$schema` field pointing to `node_modules/wrangler/config-schema.json` for autocompletion and validation.
Use `wrangler secret put API_KEY` with the interactive prompt, or pipe from a file for CI. Never pass secret values as command arguments or commit them to config; use `.dev.vars` for local development secrets.
The binding name in your code must exactly match the `binding` field in `wrangler.jsonc`. After changing config, run `wrangler types` to regenerate TypeScript definitions and verify the binding exists.
Create migrations with `wrangler d1 migrations create <db> <name>`, then apply them with `wrangler d1 migrations apply <db> --local` for development or `--remote` for production.
kartikkabadiReview Cloudflare Workers code and wrangler configuration against production best practices.
AgentiveCityConfigure structured logging, tracing, and Sentry integration for Cloudflare Workers.
sergiodxaCreate and review Cloudflare Durable Objects for stateful coordination on Workers.
partme-aiGuide Terraform infrastructure as code with HCL syntax and state management.