Skip to content
TrustedSkillsbeta
Back to all skills

Cloudflare Queues

Listed
ovachiever·vlatest·cloud

Manages Cloudflare queue configurations to optimize performance and ensure reliable request processing via automated adjustments.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add ovachiever/droid-tings --skill cloudflare-queues -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

ovachiever

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.resend.com, api.stripe.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.resend.comundeclaredapi.stripe.comundeclared

    What it found

    • skills/cloudflare-queues/templates/queues-consumer-basic.ts:76contacts api.resend.com
      const response = await fetch('https://api.resend.com/emails', {
    • skills/cloudflare-queues/templates/queues-consumer-explicit-ack.ts:107contacts api.stripe.com
      const response = await fetch('https://api.stripe.com/v1/charges', {

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned ovachiever/droid-tings at 7acd12a754.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
7acd12a754
Manifest
skills/cloudflare-queues/SKILL.md
Scanned
12 files, 4,063 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to interact directly with Cloudflare Queues, allowing them to manage message-based workloads and decouple application logic. It provides the necessary tools to enqueue tasks, monitor queue status, and handle asynchronous processing within the Cloudflare ecosystem.

When to use it

  • Asynchronous Task Processing: Offload time-consuming operations like image resizing or data transformation so your main application remains responsive.
  • Rate Limiting Management: Buffer incoming requests to prevent overwhelming backend services during traffic spikes.
  • Event-Driven Architecture: Trigger downstream workflows or notifications only after specific events are successfully recorded in the queue.
  • Worker Orchestration: Coordinate complex multi-step jobs across multiple Cloudflare Workers without managing external message brokers.

Key capabilities

  • Direct integration with the Cloudflare Queues API for real-time management.
  • Support for enqueueing messages to trigger specific worker actions.
  • Visibility into queue depth and processing status.
  • Decoupling of request handling from business logic execution.

Example prompts

  • "Set up a Cloudflare Queue to handle incoming image upload requests asynchronously."
  • "Check the current depth of my production queue and list any failed messages."
  • "Configure a worker to listen for events in the 'notifications' queue and send emails upon receipt."

Tips & gotchas

Ensure your Cloudflare Workers have the appropriate permissions to access the specific queues you intend to manage. Remember that Queues are designed for high-throughput, low-latency scenarios; complex business logic should remain outside the queue messages themselves to maintain performance.