Back to list
sickn33

upstash-qstash

by sickn33

The Ultimate Collection of 200+ Agentic Skills for Claude Code/Antigravity/Cursor. Battle-tested, high-performance skills for AI agents including official skills from Anthropic and Vercel.

1,237🍴 348📅 Jan 23, 2026

SKILL.md


name: upstash-qstash description: "Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. Use when: qstash, upstash queue, serverless cron, scheduled http, message queue serverless." source: vibeship-spawner-skills (Apache 2.0)

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:

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

Score

Total Score

95/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 1000以上

+15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

+5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon