Build stateful Durable Objects for real-time apps, WebSocket servers, coordination, and persistent state. Prevents 20 documented errors. Use when: implementing chat rooms, multiplayer games, rate limiting, session management, WebSocket hibernation, or troubleshooting class export, migration, WebSocket state loss, boolean binding, RPC streams, or binding errors.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill cloudflare-durable-objects87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, comprehensive trigger terms covering both building and troubleshooting scenarios, explicit 'Use when:' guidance, and highly distinctive terminology that clearly identifies its Cloudflare Durable Objects niche. The mention of '20 documented errors' adds credibility and signals depth of coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build stateful Durable Objects', 'real-time apps', 'WebSocket servers', 'coordination', 'persistent state', plus specific use cases like 'chat rooms', 'multiplayer games', 'rate limiting', 'session management'. | 3 / 3 |
Completeness | Clearly answers both what ('Build stateful Durable Objects for real-time apps, WebSocket servers, coordination, and persistent state') AND when with explicit 'Use when:' clause listing specific scenarios and troubleshooting contexts. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Durable Objects', 'WebSocket', 'chat rooms', 'multiplayer games', 'rate limiting', 'session management', plus specific error-related terms like 'class export', 'migration', 'binding errors' that users troubleshooting would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Cloudflare Durable Objects specifically. Terms like 'Durable Objects', 'WebSocket hibernation', 'RPC streams', and specific error types create a unique fingerprint unlikely to conflict with general WebSocket or state management skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill with excellent executable code examples and clear workflow guidance for complex operations like WebSocket hibernation and migrations. The main weakness is length - at ~600 lines with 20 inline issue descriptions, it could benefit from better progressive disclosure by moving detailed error documentation to a referenced file. The content is accurate and prevents real-world errors effectively.
Suggestions
Move the 20 documented issues to a separate 'references/known-issues.md' file and keep only a summary table with links in the main SKILL.md
Consolidate repeated patterns (e.g., class export requirements appear in Quick Start, DO Class Essentials, Critical Rules, and Issue #1) into single authoritative locations with cross-references
Consider splitting the Common Patterns section into a separate 'patterns.md' file referenced from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | While the skill is comprehensive and avoids explaining basic concepts Claude knows, it's quite lengthy (~600 lines) with some redundancy between sections (e.g., export requirements repeated multiple times, WebSocket hibernation patterns appear in multiple places). The 20 documented issues section, while valuable, could be more condensed. | 2 / 3 |
Actionability | Excellent executable code throughout - all examples are copy-paste ready with proper imports, complete function bodies, and realistic usage patterns. The Quick Start, Storage API, WebSocket Hibernation, and Common Patterns sections all provide fully working code snippets. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit validation checkpoints. The migrations section shows clear progression (v1 → v2), the WebSocket hibernation pattern includes the critical restore-in-constructor step, and the alarm retry pattern includes explicit retry count handling. The 'Critical Rules' section provides clear do/don't checklists. | 3 / 3 |
Progressive Disclosure | The skill references external files (references/top-errors.md, templates/) but these are mentioned only at the end. The document itself is monolithic with all 20 issues inline rather than in a separate reference file. The structure is good with clear sections, but the length suggests some content could be split into referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (839 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.