Executes and validates Wrangler CLI operations for Cloudflare Workers projects.
npx skills add https://github.com/sota411/codex-config --skill wrangler-sota411
Please help me install this Agent Skill. Skill: wrangler Source: https://github.com/sota411/codex-config/tree/main/user-skills/wrangler Command: npx skills add https://github.com/sota411/codex-config --skill wrangler-sota411
compatibility_date, validates bindings and environments, and regenerates types when bindings change. - Deployment & Secrets Safety: Verifies account, environment, and rollback paths before deploying, and keeps secrets out of config files, logs, and command arguments. - Use Case: When asked to deploy a Worker or debug a failing wrangler command, the Skill inspects the project's setup first, runs the correct versioned command with dry-run validation, and confirms production health after deployment. ## Quick Start Use the wrangler skill to deploy this Cloudflare Workers project using its own configured Wrangler version and verify the deployment afterwards.High-intent search queries and answers about installing and using this skill.
Use the Wrangler installation defined in the project's package.json and lockfile, invoked through the project's package manager or scripts. A missing global wrangler command does not mean the project lacks Wrangler; check node_modules and run via npx or the package runner.
Flags and config fields differ between Wrangler versions, so a command written for one version may fail on another. Check the installed version's --help output or node_modules/wrangler/config-schema.json and adapt the flags instead of silently upgrading or downgrading.
No. Install Wrangler only when the task requires it and no usable project installation exists, following the project's dependency policy and package manager. Automatically installing or upgrading to @latest can break compatibility with the project's configuration.
Keep secrets out of config files, source code, logs, and command arguments. Use Wrangler's secure interactive input, a protected input file, or CI secret injection, and keep local .dev.vars files outside version control.
No. A successful dry run or local test only validates the deployment payload, not runtime behavior. After deploying, check the deployed version and the affected behavior in production to confirm the change works.
harryy2510Retrieve up-to-date Cloudflare Workers guidance and Wrangler configuration best practices.
brainbrewlabsRoll back Kubernetes, Docker Swarm, and managed hosting deployments to a previous stable version.
jhillbhtDevelop and orchestrate Cloudflare Workers for edge webhook processing.
ClawLink-HQManage Cloudflare zones, DNS records, workers, and firewall rules via the Cloudflare API.