cf-queues

Generate Cloudflare Queues configurations and producer/consumer patterns for message processing pipelines.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/sitharaj88/claude-skills --skill cf-queues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-queues
Source: https://github.com/sitharaj88/claude-skills/tree/main/skills/cf-queues
Command: npx skills add https://github.com/sitharaj88/claude-skills --skill cf-queues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables developers to implement robust, scalable, and reliable message queuing systems directly on Cloudflare's edge network, facilitating asynchronous processing and event-driven architectures.

Core Features & Use Cases

  • Queue Creation & Management: Easily create, list, and delete Cloudflare Queues using wrangler.
  • Producer/Consumer Patterns: Implement robust patterns for sending and receiving messages, including batching, retries, and dead-letter queues.
  • Event-Driven Architectures: Build resilient systems for task queues, background processing, fan-out patterns, and real-time event handling.
  • Use Case: Automatically process uploaded images by sending messages to a queue, which then triggers image resizing and storage operations without blocking the user's request.

Quick Start

Use the cf-queues skill to generate Cloudflare Queues configurations and code for reliable message processing.

Frequently Asked Questions about cf-queues

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

FAQPage Schema
How do I set up Cloudflare Queues for asynchronous message processing at the edge?

You can generate production-ready Cloudflare Queues configurations using this skill, which provides producer and consumer patterns for asynchronous message processing. It handles queue creation via wrangler and implements reliable background task pipelines directly at the edge.

What is a dead-letter queue and how does it handle failed messages in an event-driven architecture?

A dead-letter queue captures failed messages in an event-driven architecture after retry strategies are exhausted. This mechanism ensures unreliable message processing does not block the pipeline, allowing developers to inspect and reprocess failed events later.

Can I use Cloudflare Queues to build a fan-out pattern for background processing?

Yes, you can build a fan-out pattern for background processing with Cloudflare Queues. The skill generates configurations that support broadcasting a single event to multiple consumers, enabling parallel task execution and scalable event-driven architectures.

How do I implement idempotent processing and retry strategies for serverless message queues?

Idempotent processing and retry strategies for serverless message queues are implemented through generated consumer code that safely reprocesses duplicate messages. The skill provides built-in retry logic and dead-letter handling to ensure reliable task execution without data duplication.

Does Cloudflare Queues work well for background tasks like image processing without blocking user requests?

Yes, Cloudflare Queues works well for background tasks like image processing by sending messages to a queue that trigger resizing operations asynchronously. This event-driven approach offloads heavy work from the edge, ensuring user requests remain unblocked.