mcpField
U
upstash-qstash

upstash-qstash

github.com/davila7Cloud & DevOps33.0k162 installsUpdated today
Repository

About upstash-qstash

A skill for developers building HTTP messaging flows with Upstash QStash. It covers delayed calls, scheduled jobs, and webhook delivery, along with signature verification, deduplication, and callbacks.

Key features

  1. 01Publish HTTP messages
  2. 02Schedule delayed calls
  3. 03Set up recurring jobs
  4. 04Deliver webhooks
  5. 05Verify message signatures
  6. 06Use deduplication and callbacks

Use cases

  1. 01Schedule HTTP requests for later
  2. 02Set up recurring background tasks
  3. 03Deliver webhooks reliably
  4. 04Handle failure callbacks for critical messages

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davila7/claude-code-templates --skill upstash-qstash

After installing, type/upstash-qstashin Claude Code to confirm it loaded.

Details

From the project README

Upstash QStash

You are an Upstash QStash expert who builds reliable serverless messaging without infrastructure management. You understand that QStash's simplicity is its power - HTTP in, HTTP out, with reliability in between.

You've scheduled millions of messages, set up cron jobs that run for years, and built webhook delivery systems that never drop a message. You know that QStash shines when you need "just make this HTTP call later, reliably."

Your core philosophy:

  1. HTTP is the universal language - no c

Capabilities

  • qstash-messaging
  • scheduled-http-calls
  • serverless-cron
  • webhook-delivery
  • message-deduplication
  • callback-handling
  • delay-scheduling
  • url-groups

Patterns

Basic Message Publishing

Sending messages to be delivered to endpoints

Scheduled Cron Jobs

Setting up recurring scheduled tasks

Signature Verification

Verifying QStash message signatures in your endpoint

Anti-Patterns

❌ Skipping Signature Verification
❌ Using Private Endpoints
❌ No Error Handling in Endpoints

⚠️ Sharp Edges

IssueSeveritySolution
Not verifying QStash webhook signaturescritical# Always verify signatures with both keys:
Callback endpoint taking too long to respondhigh# Design for fast acknowledgment:
Hitting QStash rate limits unexpectedlyhigh# Check your plan limits:
Not using deduplication for critical operationshigh# Use deduplication for critical messages:
Expecting QStash to reach private/localhost endpointscritical# Production requirements:
Using default retry behavior for all message typesmedium# Configure retries per message:
Sending large payloads instead of referencesmedium# Send references, not data:
Not using callback/failureCallback for critical flowsmedium# Use callbacks for critical operations:

Related Skills

Works well with: vercel-deployment, nextjs-app-router, redis-specialist, email-systems, supabase-backend, cloudflare-workers

Comments

Markdown supported