upstash-qstash
Implement serverless message queues and scheduled tasks using Upstash QStash.
Install
mkdir -p .claude/skills/upstash-qstash && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2242" && unzip -o skill.zip -d .claude/skills/upstash-qstash && rm skill.zipInstalls to .claude/skills/upstash-qstash
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Schedule recurring background tasks
- →Implement serverless webhook delivery
- →Manage delayed message queues
- →Verify QStash webhook signatures
- →Configure message deduplication
How it works
QStash acts as an HTTP-based message queue that handles task delivery, retries, and scheduling, allowing serverless functions to offload work without managing infrastructure.
Inputs & outputs
When to use upstash-qstash
- →Schedule recurring background tasks
- →Implement serverless webhook delivery
- →Manage delayed message queues
- →Verify QStash webhook signatures
About this skill
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
When not to use it
- →Directly calling private or localhost endpoints
- →Sending large payloads instead of references
Prerequisites
Limitations
- →Subject to plan-specific rate limits
- →Requires signature verification for security
How it compares
It provides a managed, reliable HTTP-in/HTTP-out interface for task scheduling, removing the need for custom infrastructure to handle retries and cron jobs.
Compared to similar skills
upstash-qstash side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| upstash-qstash (this skill) | 6 | 6mo | No flags | Intermediate |
| mqtt-uns-feeder | 0 | 2mo | No flags | Advanced |
| freshservice-automation | 0 | 3mo | No flags | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by davila7
View all by davila7 →You might also like
mqtt-uns-feeder
clemensv
Use when adding MQTT/Unified-Namespace transport to a feeder in this repo — either alongside an existing Kafka feeder (transport split) or for a brand-new source where MQTT is the primary fit. Covers UNS topic-tree design, xRegistry MQTT messagegroup pattern, paho-mqtt v5 binary-mode CloudEvent emis
freshservice-automation
KevanPatira
Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
applescript
martinholovsky
Expert in AppleScript and JavaScript for Automation (JXA) for macOS system scripting. Specializes in secure script execution, application automation, and system integration. HIGH-RISK skill due to shell command execution and system-wide control capabilities.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
azure-devops-rest-api
Tiberriver256
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.