Guides Cloudflare Workers deployment, configuration, and resource management via the Wrangler CLI.
npx skills add https://github.com/tarabakz25/my-skills --skill wrangler-tarabakz25
Please help me install this Agent Skill. Skill: wrangler Source: https://github.com/tarabakz25/my-skills/tree/main/wrangler Command: npx skills add https://github.com/tarabakz25/my-skills --skill wrangler-tarabakz25
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 over TOML, compatibility dates, type generation via wrangler types, and secure secret handling. - Use Case: When asked to deploy a Worker with a D1 database and KV cache, the agent first checks the latest docs, writes a valid wrangler.jsonc with correct bindings, runs migrations, and deploys with the correct flags. ## Quick Start Ask the agent to deploy your Cloudflare Worker or configure a binding, and it will verify Wrangler is installed and use current documentation for correct syntax.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.
Add binding arrays to wrangler.jsonc: `d1_databases` with database_name and database_id, `kv_namespaces` with the namespace id, and `r2_buckets` with the bucket name. Run `wrangler types` afterward to regenerate TypeScript definitions.
Prefer wrangler.jsonc because newer Wrangler features are JSON-only. Include the $schema field pointing to node_modules/wrangler/config-schema.json for editor validation and autocompletion.
Use `wrangler secret put KEY` with the 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 that is not committed.
The binding name in your code must exactly match the binding name in wrangler.jsonc. After changing config, run `wrangler types` to update TypeScript definitions and restart `wrangler dev` so the new bindings load.
Yes, `wrangler dev` runs a local server with simulated bindings by default. Set `remote: true` on specific bindings to connect to real resources, and use @cloudflare/vitest-pool-workers for automated testing.
dallayAutomate Wrangler CLI workflows for Cloudflare Workers deployments.
AgentiveCityConfigure structured logging, tracing, and Sentry integration for Cloudflare Workers.
LAF-USAutomate Cloudflare Wrangler workflows for deploying and managing Workers.
biwakonbuManage Cloudflare resources as code using Terraform and Pulumi.