workers-best-practices

Review Cloudflare Workers code and validate wrangler.jsonc configurations.

Updated Mar 12, 2026

Search Tags:#code review #best practices #security #cloudflare workers #observability #wrangler #type validation

Ready to run

npx skills add https://github.com/mpsuesser/workspace --skill workers-best-practices-mpsuesser

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workers-best-practices
Source: https://github.com/mpsuesser/workspace/tree/main/dotconfig/pi/agent/skills/.deprecated/cloudflare/workers-best-practices
Command: npx skills add https://github.com/mpsuesser/workspace --skill workers-best-practices-mpsuesser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps prevent production incidents and insecure code by catching common Cloudflare Workers mistakes before deployment.

Core Features & Use Cases

Workers code review against current best practices: Flags issues like streaming misuse, floating promises, global request state, weak observability, and insecure patterns.
Type- and config-aware validation: Verifies binding types, handler signatures, wrangler.jsonc fields, compatibility settings, secrets usage, and schema correctness using retrieval-first steps.
Evidence-based guidance: Ensures recommendations are grounded in the latest Cloudflare Workers best-practices page, types, and wrangler schema rather than assumptions.

Quick Start

Ask the AI to review a Cloudflare Worker implementation for best-practice compliance, including streaming, promise handling, config/binding correctness, and security concerns.

Frequently Asked Questions about workers-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review my Cloudflare Workers code for production readiness?▼

Review Cloudflare Workers code for production readiness by validating handler signatures, wrangler.jsonc fields, and compatibility settings against current best practices. This process identifies anti-patterns involving streaming, floating promises, global state, and secrets to reduce deployment risk.

What common anti-patterns cause production incidents in Cloudflare Workers?▼

Common anti-patterns causing production incidents include streaming misuse, floating promises, global request state, weak observability, and insecure secrets handling. Identifying these issues before deployment prevents insecure code and reduces production risk.

How do I validate my wrangler.jsonc configuration and binding types?▼

Validate wrangler.jsonc configuration and binding types by retrieving the wrangler config-schema.json and @cloudflare/workers-types. This type- and config-aware validation verifies schema correctness, binding types, and compatibility settings based on retrieved evidence.

Can I check my Cloudflare Workers implementation for security and observability issues?▼

Check Cloudflare Workers implementations for security and observability issues by applying evidence-based guidance. This flags insecure patterns and weak observability configurations, ensuring recommendations are grounded in the latest best practices rather than assumptions.

What's the best way to ensure my Cloudflare Workers recommendations are evidence-based?▼

Ensure Cloudflare Workers recommendations are evidence-based by retrieving the latest best-practices content, @cloudflare/workers-types, and wrangler config-schema.json. Checking patterns and types against these sources produces grounded fix suggestions without relying on assumptions.