workers-binding-validator

Validate Cloudflare Workers binding configuration against wrangler.toml and TypeScript Env interfaces.

3|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/hirefrank/claude-plugins --skill workers-binding-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workers-binding-validator
Source: https://github.com/hirefrank/claude-plugins/tree/main/plugins/edge-stack/skills/workers-binding-validator
Command: npx skills add https://github.com/hirefrank/claude-plugins --skill workers-binding-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically validates that code bindings align with wrangler.toml configuration and TypeScript Env interfaces, reducing binding drift.

Core Features & Use Cases

  • Binding Consistency: Checks code references against wrangler.toml.
  • Interface Validation: Verifies Env interface matches actual bindings.
  • Binding Type Accuracy: Ensures correct KV/R2/D1/DO binding usage.

Quick Start

Review a Workers project to verify binding names and types against configuration.

Frequently Asked Questions about workers-binding-validator

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

FAQPage Schema
How do I validate that my Cloudflare Workers bindings match wrangler.toml?

Binding validation checks that code references to KV, R2, D1, and Durable Objects align with your wrangler.toml configuration and TypeScript Env interface, catching mismatches before deployment.

Why would my TypeScript Env interface not match my actual bindings?

When you update wrangler.toml bindings or add new service references, the Env interface can drift out of sync. Validation detects these gaps between declared types and actual configuration.

Can I validate remote and secret bindings in my Workers project?

Yes, validation covers remote binding configuration for development environments and distinguishes between secret bindings and environment variables to ensure correct access patterns.

How do I check if my binding names and types are correct across KV, R2, and D1?

Binding type accuracy checks verify that each resource reference—whether KV namespace, R2 bucket, D1 database, or Durable Object—uses the correct binding type in your code and configuration.

What happens when I add new bindings to wrangler.toml but forget to update my code?

Binding consistency validation detects unused or missing bindings in your code by comparing wrangler.toml declarations against actual env parameter usage, surfacing configuration drift.