Agent skill · Workflow & Productivity

upstash-qstash

Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure.

Nick44,414★ · +328/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill upstash-qstash --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 24 KB
Bundled scripts: none
Path: skills/upstash-qstash/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Guides an agent to implement and manage Upstash QStash-based workflows, including sending messages, scheduling, webhook verification, delivery callbacks, URL group fan-out, deduplication, and handling common edge cases. Emphasizes reliability, signatures verification, and observability through callbacks and status updates.

How it works

  • Provides examples and patterns for:
    • Basic message publishing with optional delay
    • Scheduled cron-like jobs via QStash schedules
    • Signature verification for incoming webhooks using Receiver with current and next signing keys
    • Callbacks and failure callbacks to receive delivery status
    • URL groups to broadcast to multiple endpoints
    • Message deduplication using deduplicationId and contentBasedDeduplication
  • Shows configuration and runtime usage via the qstash-sdk in several frameworks and environments (Next.js, Cloudflare Workers, Vercel, AWS Lambda, Netlify Functions)
  • Demonstrates defensive and operational patterns:
    • Fast webhook responses to avoid timeouts
    • Offloading heavy work to subsequent messages or queues
    • Handling rate limits, retries, and batch publishing
    • Ensuring endpoints are public and HTTPS is used
  • Includes Notable edge-cases and mitigations for:
    • Verifying signatures with two keys during rotation
    • Avoiding localhost or private endpoints for public QStash reachability
    • Managing large payloads by sending references instead of full documents
    • Configuring per-message retries and backoff strategies

When to use it

  • When you need reliable, serverless HTTP-based task delivery without managing infrastructure
  • When initial integration requires scheduled or delayed tasks, webhook delivery, and deduplication for idempotent processing
  • When you must verify inbound webhook signatures and track delivery outcomes via callbacks
  • When sending to multiple endpoints or requiring URL groups and structured retry logic

What it can touch

  • Interacts with Upstash QStash via the qstash-sdk
  • Uses public HTTP(S) endpoints for delivery
  • May require environment variables for QStash tokens and signing keys

Caveats

  • Declared risk: critical
  • Notable risk areas include not verifying QStash webhook signatures, potential heavy processing in callbacks causing timeouts, and rate-limit handling requirements
  • Requires endpoints to be publicly accessible over HTTPS; localhost or private IPs are not reachable by QStash
  • Large payloads should be avoided; prefer sending references and fetching data in the handler
From the SKILL.md

# Upstash QStash Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. ## Principles - HTTP is the interface - if it speaks HTTPS, it speaks QStash - Endpoints must be public - QStash calls your URLs from the cloud - Verify signatures always - never trust unverified webhooks - Schedules are fire-and-forget - QStash handles the cron - Retries are built-in - but configure them for your use case - Delays are free - schedule seconds to days in the future - Callbacks complete the loop - know when delivery succeeds or fails - Deduplication prevents double-processing - use message IDs ## Capabilities - qstash-messaging - scheduled-http-calls - serverless-cron - webhook-delivery - message-deduplication - callback-handling - delay-scheduling - url-groups ## Scope - complex-workflows -> inngest - redis-queues -> bullmq-specialist - event-sourcing -> event-architect - workflow-orchestration -> temporal-craftsman ## Tooling ### Core - qstash-sdk - upstash-console ### Frameworks - nextjs - cloudflare-workers - vercel-functions - aws-lambda - netlify-functions ### Patterns - scheduled-jobs - delayed-messages -

What's inside
Steps it walks through
  1. Principles
  2. Capabilities
  3. Scope
  4. Tooling
  5. Core
  6. Frameworks
  7. Patterns
  8. Related
  9. Basic Message Publishing
  10. Scheduled Cron Jobs
  11. Signature Verification
  12. Callback for Delivery Status
  13. URL Groups (Fan-out)
  14. Message Deduplication
Commands it runs
ngrok http 3000
Use the ngrok URL for QStash testing
More from agentic-awesome-skills
All skills →
About this skill
What does the upstash-qstash skill do?

Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill upstash-qstash --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going