Deploy and manage Cloudflare Workers, KV, R2, D1, and other bindings using the Wrangler CLI.
npx skills add https://github.com/leonardoacosta/agents --skill wrangler-leonardoacosta
Please help me install this Agent Skill. Skill: wrangler Source: https://github.com/leonardoacosta/agents/tree/main/skills/wrangler Command: npx skills add https://github.com/leonardoacosta/agents --skill wrangler-leonardoacosta
wrangler dev, wrangler deploy, dry runs, environments, versions, and rollback workflows. - Resource Management: Provides command references for KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Queues, Containers, Workflows, Pipelines, and Secrets Store. - Configuration Guidance: Recommends wrangler.jsonc with correct binding shapes, compatibility dates, remote bindings, and type generation via wrangler types. - Use Case: When asked to deploy a Worker with a D1 database and R2 bucket, the agent first checks the latest docs and config schema, then writes a valid wrangler.jsonc and runs the correct deploy commands. ## Quick Start Ask the agent to create and deploy a new Cloudflare Worker with a D1 database binding 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, main entry point, and compatibility_date. Use `wrangler deploy --dry-run` to validate first, and `wrangler deploy --env staging` to target a specific environment.
Create a migration with `wrangler d1 migrations create <db> <name>`, then apply it locally with `wrangler d1 migrations apply <db> --local` or to production with `--remote`. List pending migrations using `wrangler d1 migrations list <db>`.
Prefer wrangler.jsonc because newer Wrangler features are JSON-only. Add the $schema field pointing to node_modules/wrangler/config-schema.json for validation and autocompletion of binding shapes.
By default, wrangler dev simulates bindings locally. Set `"remote": true` on specific bindings like R2, Vectorize, or AI in your config to connect to real resources while running the Worker locally.
Use `wrangler secret put KEY` for an interactive prompt, or pipe from a file for CI. Never pass secret values as command arguments or echo them. For local development, store secrets in a .dev.vars file.
The binding name in your Worker code must exactly match the binding name in wrangler.jsonc. After changing config, run `wrangler types` to regenerate TypeScript definitions and catch mismatches.
firstsun-devReviews and authors Cloudflare Workers code against production best practices and current type definitions.
AgentiveCityConfigure structured logging, tracing, and Sentry integration for Cloudflare Workers.
eykdConfigure and run Cloudflare Workers tests with D1 and KV bindings.
watzonManage Cloudflare services and configurations using Wrangler CLI and REST API scripts.