Deploy and manage Cloudflare Workers, bindings, and resources using the Wrangler CLI.
npx skills add https://github.com/kveperedo/website --skill wrangler-kveperedo
Please help me install this Agent Skill. Skill: wrangler Source: https://github.com/kveperedo/website/tree/main/.agents/skills/wrangler Command: npx skills add https://github.com/kveperedo/website --skill wrangler-kveperedo
wrangler dev, wrangler deploy, environments, secrets management, 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, compatibility dates, type generation via wrangler types, and remote bindings for local development. - Use Case: You need to add a Hyperdrive binding to your Worker and deploy it to a staging environment. The Skill fetches the latest config schema, writes the correct wrangler.jsonc binding, and runs wrangler deploy --env staging with a dry run first. ## Quick Start Ask the AI to configure and deploy your Cloudflare Worker with the correct bindings using current Wrangler syntax.High-intent search queries and answers about installing and using this skill.
Run `wrangler deploy` after defining your Worker in wrangler.jsonc with a 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.
Use `wrangler secret put API_KEY` for an interactive prompt, or `wrangler secret bulk secrets.json` for multiple secrets. Never pass secret values as command arguments or echo them, and use `.dev.vars` for local development secrets.
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.
By default `wrangler dev` uses local storage simulation for bindings. Set `"remote": true` on specific bindings in your config to connect to real resources, which is required for Workers AI and recommended for Vectorize.
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.
Run `wrangler rollback` to revert to the previous version, or `wrangler rollback <VERSION_ID>` for a specific version. Use `wrangler versions list` to see recent deployments and their IDs.
nicholasgriffintnAutomate Cloudflare Workers deployment and management tasks via the Wrangler CLI.
AgentiveCityConfigure structured logging, tracing, and Sentry integration for Cloudflare Workers.
eykdConfigure and run Cloudflare Workers tests with D1 and KV bindings.
biwakonbuManage Cloudflare resources as code using Terraform and Pulumi.