cloudflare-queues
Build async message queues with Cloudflare Queues for background processing. Use when: handling async tasks, batch processing, implementing retries, configuring dead letter queues, managing consumer concurrency, or troubleshooting queue timeout, batch retry, message loss, or throughput exceeded. Prevents 13 documented errors including multi-dev limitations, remote binding conflicts, and DLQ issues.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill cloudflare-queues87
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 key criteria. It provides specific capabilities, comprehensive trigger terms covering both implementation and troubleshooting scenarios, explicit 'Use when' guidance, and platform-specific terminology that makes it highly distinctive. The mention of '13 documented errors' adds credibility and specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build async message queues', 'background processing', 'handling async tasks', 'batch processing', 'implementing retries', 'configuring dead letter queues', 'managing consumer concurrency'. Also mentions specific error types it addresses. | 3 / 3 |
Completeness | Clearly answers both what ('Build async message queues with Cloudflare Queues for background processing') and when (explicit 'Use when:' clause with multiple trigger scenarios including both feature implementation and troubleshooting contexts). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'async tasks', 'batch processing', 'retries', 'dead letter queues', 'consumer concurrency', 'queue timeout', 'batch retry', 'message loss', 'throughput exceeded', 'Cloudflare Queues'. These are terms developers naturally use when working with message queues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Cloudflare Queues (not generic queuing), mentions platform-specific issues like 'multi-dev limitations', 'remote binding conflicts', and 'DLQ issues'. Unlikely to conflict with other skills due to Cloudflare-specific terminology. | 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 workflows for queue operations. The comprehensive coverage of known issues and error prevention is valuable for production use. However, the document is quite long and could benefit from better progressive disclosure by moving detailed reference sections to separate files.
Suggestions
Split Known Issues Prevention, Event Subscriptions, and HTTP Publishing sections into separate reference files (e.g., KNOWN-ISSUES.md, EVENTS.md) with brief summaries and links in the main skill
Consolidate the repeated DLQ warnings into a single prominent callout rather than mentioning it in multiple sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated DLQ warnings, multiple similar code examples). The extensive known issues section and community tips add value but could be more condensed. Some sections like pricing calculations are detailed beyond what Claude needs. | 2 / 3 |
Actionability | Excellent executable code throughout with copy-paste ready examples for producers, consumers, DLQ setup, error handling, and troubleshooting. All code snippets are complete TypeScript/bash with proper imports and context. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints. The Quick Start has numbered steps, DLQ setup includes verification, and troubleshooting sections provide diagnostic commands. Critical patterns section explicitly shows ack-on-success patterns for non-idempotent operations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a logical flow from Quick Start to advanced topics. However, this is a monolithic 600+ line file that could benefit from splitting advanced topics (Known Issues, Event Subscriptions, HTTP Publishing) into separate reference files with links. | 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 (937 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 | |
- Reviewed
Table of Contents
Is this your skill?
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.