queue

Implement a serverless background job queue with Inngest and PostgreSQL.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mattwoodco/skills --skill queue-mattwoodco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: queue
Source: https://github.com/mattwoodco/skills/tree/main/skills/queue
Command: npx skills add https://github.com/mattwoodco/skills --skill queue-mattwoodco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires db, env-config, auth, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a robust, serverless background job queue solution, eliminating the need for Redis or dedicated worker processes, and ensuring jobs survive crashes with automatic retries and progress tracking.

Core Features & Use Cases

  • Durable Background Jobs: Run asynchronous tasks that persist through application restarts and failures.
  • Progress Tracking & History: Monitor job execution status and view historical data.
  • Serverless Compatibility: Works seamlessly on platforms like Vercel without managing infrastructure.
  • Use Case: Implement a background image processing task that resizes uploaded images, or send out bulk emails asynchronously without blocking the user interface.

Quick Start

Use the queue skill to submit a new background job of type 'example' with the prompt 'Generate a report'.

Frequently Asked Questions about queue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run serverless background jobs in Next.js without managing Redis or worker processes?

Serverless background jobs in Next.js can run without Redis or dedicated workers by using Inngest for durable, retriable asynchronous task execution. This approach manages job status and progress directly in a PostgreSQL database via Drizzle ORM.

What is the best way to track the status and progress of async tasks in a serverless environment?

Tracking async task status and progress in a serverless environment involves persisting job execution data in a PostgreSQL database via Drizzle ORM. This ensures historical job data and execution states survive application restarts and failures.

Can I use Inngest with Next.js and PostgreSQL for durable function execution?

Inngest works seamlessly with Next.js and PostgreSQL for durable function execution. It integrates directly with Drizzle ORM to persist job results, ensuring asynchronous tasks survive crashes with automatic retries.

How do I process bulk emails or image transformations asynchronously without blocking the user interface?

Processing bulk emails or image transformations asynchronously without blocking the UI requires submitting background jobs to a queue. Inngest handles the durable execution, allowing tasks to run independently of the main application thread.

Do I need a dedicated database to manage background job history with Inngest?

A PostgreSQL database is required to manage background job history with Inngest. The queue system uses Drizzle ORM to persist job status, progress tracking, and execution results directly within your existing database setup.