Agent skill · software engineering · secondsky
cloudflare-queues
This skill should be used when the user asks to \"set up Cloudflare Queues\", \"create a message queue\", \"implement queue consumer\", \"process background jobs\", \"configure queue retry logic\", \"publish messages to queue\", \"implement dead letter queue\", or encountering \"queue timeout\", \"message retry\", \"throughput exceeded\", \"queue backlog\" errors.
Why this skill is useful
Provides specific commands and configuration patterns for setting up and managing Cloudflare Queues that the AI wouldn't reliably generate on its own.
What it needs
Requires bun, wrangler installed locally. Requires cloudflare account access. About 8k tokens when loaded. Last updated 2026-08-06. 204 stars on the source repository.
What this skill does
Cloudflare Queues Status: Production Ready ✅ Last Verified: 2025-12-27 Dependencies: cloudflare-worker-base (for Worker setup) Contents: Quick Start • Critical Rules • Top Errors • Use Cases • When to Load References • Limits --- Quick Start (10 Minutes) 1. Create Queue 2. Producer (Send Messages) wrangler.jsonc: src/index.ts: 3. Consumer (Process Messages) wrangler.jsonc: src/consumer.ts: Deploy: Load: references/setup-guide.md for complete 6-step setup with DLQ configuration --- Critical Rules Always Do ✅ 1. Configure Dead Letter Queue for production queues 2. Use explicit ack() for non-idempotent operations (DB writes, API calls) 3. Validate message size before sending (<128 KB) 4. Use sendBatch() for multiple messages (more efficient) 5. Implement exponential backoff for retries 6. Set appropriate batch settings based on workload 7. Monitor queue backlog and consumer errors 8. Use ctx.waitUntil() for async cleanup in consumers 9. Handle errors gracefully - log, alert, retry 10. Let concurrency auto-scale (don't set maxconcurrency unless needed) Never Do ❌ 1. Never assume message ordering - not guaranteed FIFO 2. Never rely on implicit ack for non-idempotent ops - use explicit ack() 3. Never send messages >128 KB - will fail 4. Never delete queues with active messages - data loss 5. Never skip DLQ configuration in production 6. Never exceed 5000 msg/s per queue - rate limit error 7. Never process messages synchronously in loop - use Promise.all() 8. Never ignore message.attempts - use for backoff logic 9. Never set maxconcurrency=1 unless you have a very specific reason 10. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills secondsky/cloudflare-queues