Agent skill · software engineering · aiskillstore
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Why this skill is useful
Provides specific patterns and configurations for Durable Objects that the AI wouldn't reliably generate on its own.
What it needs
Requires wrangler installed locally. Requires cloudflare account access. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Durable Objects Build stateful, coordinated applications on Cloudflare's edge using Durable Objects. Retrieval Sources Your knowledge of Durable Objects APIs and configuration may be outdated. Prefer retrieval over pre-training for any Durable Objects task. Resource URL ---------- ----- Docs https://developers.cloudflare.com/durable-objects/ API Reference https://developers.cloudflare.com/durable-objects/api/ Best Practices https://developers.cloudflare.com/durable-objects/best-practices/ Examples https://developers.cloudflare.com/durable-objects/examples/ Fetch the relevant doc page when implementing features. When to Use Creating new Durable Object classes for stateful coordination Implementing RPC methods, alarms, or WebSocket handlers Reviewing existing DO code for best practices Configuring wrangler.jsonc/toml for DO bindings and migrations Writing tests with @cloudflare/vitest-pool-workers Designing sharding strategies and parent-child relationships Reference Documentation ./references/rules.md - Core rules, storage, concurrency, RPC, alarms ./references/testing.md - Vitest setup, unit/integration tests, alarm testing ./references/workers.md - Workers handlers, types, wrangler config, observability Search: blockConcurrencyWhile, idFromName, getByName, setAlarm, sql.exec Core Principles Use Durable Objects For Need Example ------ --------- Coordination Chat rooms, multiplayer games, collaborative docs Strong consistency Inventory, booking systems, turn-based games Per-entity storage Multi-tenant SaaS, per-user data Persistent connections WebSockets, real-time notifications Scheduled work per entity Subscription renewals, game timeouts Do NOT Use For Stateless request handling (use plain Workers) Maximum global distribution needs High fan-out independent requests Quick Reference Wrangler Configuration Basic Durable Object Pattern Critical Rules 1. Model around coordination atoms - One DO per chat room/game/user, not one global DO 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/durable-objects