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
- 01Publish HTTP messages
- 02Schedule delayed calls
- 03Set up recurring jobs
- 04Deliver webhooks
- 05Verify message signatures
- 06Use deduplication and callbacks
Use cases
- 01Schedule HTTP requests for later
- 02Set up recurring background tasks
- 03Deliver webhooks reliably
- 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-qstashAfter installing, type/upstash-qstashin Claude Code to confirm it loaded.
Details
From the project READMEUpstash 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:
- 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
| Issue | Severity | Solution |
|---|---|---|
| Not verifying QStash webhook signatures | critical | # Always verify signatures with both keys: |
| Callback endpoint taking too long to respond | high | # Design for fast acknowledgment: |
| Hitting QStash rate limits unexpectedly | high | # Check your plan limits: |
| Not using deduplication for critical operations | high | # Use deduplication for critical messages: |
| Expecting QStash to reach private/localhost endpoints | critical | # Production requirements: |
| Using default retry behavior for all message types | medium | # Configure retries per message: |
| Sending large payloads instead of references | medium | # Send references, not data: |
| Not using callback/failureCallback for critical flows | medium | # Use callbacks for critical operations: |
Related Skills
Works well with: vercel-deployment, nextjs-app-router, redis-specialist, email-systems, supabase-backend, cloudflare-workers