Wrangler

**Judgement:** Wrangler is a strong, focused skill for managing Cloudflare Workers and related data services via the official Wrangler CLI. It is well-suited for infrastructure- and deployment-oriented workflows that already rely on Cloudflare’s serverless stack. **Strengths:** - Broad coverage of key Cloudflare surfaces: Workers deploy/rollback, logs, KV, D1, R2, queues, and secrets. - Clear, command-centric documentation that mirrors Wrangler’s official usage. - Supports modern configuration patterns (TOML/JSON/JSONC) and bindings for KV/D1/R2/assets. **Risks / Limitations:** - High blast radius: this skill can delete workers, KV namespaces, databases, and buckets, or deploy bad configs, directly impacting production. - Requires correct Cloudflare authentication and Node.js v20+; failures in auth or environment setup will block operations. - Does **not** manage DNS, custom domains, WAF, or SSL; attempting those tasks requires other tools (e.g., a dedicated Cloudflare API skill). **Recommended scenarios:** - You explicitly want to deploy, update, or roll back Cloudflare Workers or manage associated KV/D1/R2 resources via Wrangler. - You need scripted/automated operational tasks like running D1 migrations, exporting databases, or tailing worker logs. - You already have DNS/custom domains handled elsewhere and only need the application/runtime and data-layer management. Use with extra human review for any destructive or production-affecting commands (deletes, schema changes, mass KV/R2 operations).