Back to catalog / Developer tools
Workers best practices: review against project target and compatibility date
Check APIs, bindings, observability, and failure patterns against docs and local schema.
Skills
Read the project’s Wrangler config, compatibility date, installed dependencies, and generated `wrangler types`. Retrieve relevant official docs and the installed schema. Check unbounded response buffering, hard-coded secrets, `Math.random` security tokens, unattached background work, mutable module-level request state, REST where bindings exist, misuse of `passThroughOnException`, handwritten Env drift, and destructured ctx methods. Explain runtime impact before changing compatibility date, logs/traces, or bindings; regenerate types and run focused type/runtime tests. Do not deploy solely because a review recommends it.
Permissions
Prerequisites
- Write, review, or configure Workers with attention to compatibility, bindings, runtime, security, and observability.
Permissions
- May edit Worker code, Wrangler config, logs/traces, and binding types.
Limitations
Use installed version, generated types, and current compatibility date; test and authorize runtime/deploy changes.
Pinned upstream source
- Repository
- cloudflare/skills
- File path
- skills/workers-best-practices/SKILL.md
- Pinned commit
53395984c3ea1925d00fce03b266112302f050e6- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
Workers documentation · installed Wrangler schema · generated platform types
Main topic
Take a coding Agent change from context to verification