upstash-qstash▌
davila7/claude-code-templates · updated Apr 8, 2026
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.
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:
- 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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★36 reviews- ★★★★★Nikhil Martinez· Dec 28, 2024
upstash-qstash is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Zaid Haddad· Dec 20, 2024
Registry listing for upstash-qstash matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Shikha Mishra· Dec 12, 2024
Useful defaults in upstash-qstash — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Nikhil Robinson· Dec 8, 2024
upstash-qstash fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yuki Kapoor· Nov 19, 2024
upstash-qstash reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yuki Jain· Nov 11, 2024
Keeps context tight: upstash-qstash is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yash Thakker· Nov 3, 2024
upstash-qstash has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dhruvi Jain· Oct 22, 2024
Solid pick for teams standardizing on skills: upstash-qstash is focused, and the summary matches what you get after install.
- ★★★★★Diya Thompson· Oct 10, 2024
Registry listing for upstash-qstash matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kiara Kapoor· Oct 2, 2024
upstash-qstash is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 36