← LeaderboardThe Skill Leaderboard

upstash-qstash

Skill file plugins/agentic-awesome-skills/skills/upstash-qstash/SKILL.md in sickn33/agentic-awesome-skills. Read the publisher’s upstream source.

Description could not be read from the source metadata.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

upstash-qstash

Start a fresh conversation. Replace the highlighted placeholders.

Use upstash-qstash to implement a reliable QStash-delivered HTTP task in [project path and workflow details], using the existing environment-based QStash configuration; require a public HTTPS destination, verify every QStash request and callback signature using the raw request body and both signing keys, and add deduplication plus retry/error handling appropriate to the operation.

Required inputs

  • [project path and workflow details]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: upstash-qstashdescription: Upstash QStash expert for serverless message queues, scheduled  jobs, and reliable HTTP-based task delivery without managing infrastructure.risk: criticalsource: vibeship-spawner-skills (Apache 2.0)date_added: 2026-02-27

Upstash QStash

Upstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

  • User mentions or implies: qstash
  • User mentions or implies: upstash queue
  • User mentions or implies: serverless cron
  • User mentions or implies: scheduled http
  • User mentions or implies: message queue serverless
  • User mentions or implies: vercel cron
  • User mentions or implies: delayed message

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.