@tank/cloudflare-workers

Design Cloudflare Workers applications with Wrangler, bindings, and edge primitives.

1|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-cloudflare-workers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @tank/cloudflare-workers
Source: https://github.com/tankpkg/packages/tree/main/skills/cloudflare-workers
Command: npx skills add https://github.com/tankpkg/packages --skill tank-cloudflare-workers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design, build, test, and deploy Cloudflare Workers applications without falling into common edge-runtime, binding, or deployment mistakes. It reduces confusion around when to use Workers, Pages Functions, Hono, or the different Cloudflare storage and coordination primitives.

Core Features & Use Cases

  • Runtime guidance: Choose Web API-first patterns for request handling, routing, middleware, and background work in Workers.
  • Platform decisions: Select the right Cloudflare primitive for each job, including KV, D1, R2, Durable Objects, Queues, Vectorize, and Workers AI.
  • Delivery and reliability: Plan Wrangler configuration, environment separation, testing with Miniflare and Vitest, observability, performance tuning, and security hardening.
  • Use case: An engineer shipping an edge API can use this Skill to decide the app structure, define bindings, validate local behavior, and roll out safely across preview, staging, and production.

Quick Start

Ask the Skill to help you architect, test, and deploy a Cloudflare Workers app for your specific use case.

Frequently Asked Questions about @tank/cloudflare-workers

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

FAQPage Schema
How do I structure a Cloudflare Workers application with the right bindings and routing?

To structure a Cloudflare Workers application, apply Web API-first runtime patterns for request handling and routing, define environment-scoped bindings, and select platform-specific primitives like KV, D1, R2, or Durable Objects based on your edge workload.

What's the best way to test Cloudflare Workers locally before deploying to production?

The best way to test Cloudflare Workers locally is using Miniflare and Vitest to validate edge-safe dependencies and local behavior before rolling out safely across preview, staging, and production environments.

When should I use Durable Objects versus KV or D1 for state management in Cloudflare Workers?

Use Durable Objects for stateful coordination and strong consistency, KV for eventually consistent reads, and D1 for relational database queries, matching the Cloudflare primitive to your specific data requirements.

Can I use the Hono framework to build edge APIs on Cloudflare Workers?

Yes, Hono is a supported platform-specific primitive for building edge APIs on Cloudflare Workers, providing routing and middleware capabilities within the Web API-first edge runtime environment.

What are common limitations when migrating applications to the Cloudflare Workers edge runtime?

Common Cloudflare Workers limitations include avoiding Node.js-specific APIs in favor of Web API-first patterns, ensuring edge-safe dependencies, and properly scoping bindings to distinct environments to prevent runtime constraints.

How does Wrangler configuration impact Cloudflare Workers deployment and environment separation?

Wrangler configuration manages Cloudflare Workers deployment workflows by defining environment separation, bindings setup, and observability rules to ensure safe production rollouts.