trigger-tasks

Build durable background tasks, scheduled jobs, and AI agent workflows with Trigger.dev.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/celeroncoder/skills --skill trigger-tasks-celeroncoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trigger-tasks
Source: https://github.com/celeroncoder/skills/tree/main/trigger-tasks
Command: npx skills add https://github.com/celeroncoder/skills --skill trigger-tasks-celeroncoder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @trigger.dev/sdk, zod, and includes references (resource) components.

What problem does it solve? Long-running jobs, webhook processing, and recurring work often fail silently or block your main application when handled with ad-hoc code. This Skill provides the patterns to build durable background tasks with automatic retries, queuing, and observability using Trigger.dev. ## Core Features & Use Cases - Durable Task Execution: Define tasks with automatic retries, exponential backoff, idempotency keys, and machine presets using @trigger.dev/sdk. - Scheduling & Concurrency: Create cron-based scheduled tasks with timezone support, plus queues, per-tenant concurrency limits, and debouncing for webhook bursts. - Orchestration & Observability: Trigger tasks from backend code or other tasks, wait on results safely, and track progress with metadata and tags. - Use Case: Imagine you need to process uploaded files for thousands of users without blocking your API. Use this Skill to create a queued task with per-user concurrency limits, retry logic for flaky external APIs, and metadata-based progress tracking. ## Quick Start Use the trigger-tasks skill to create a Trigger.dev background task that processes uploaded files with retries and a concurrency-limited queue.

Frequently Asked Questions about trigger-tasks

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

FAQPage Schema
How do I create a background task with Trigger.dev?▼

Define a task using the task function from @trigger.dev/sdk with a unique id and a run function, then export it from your trigger directory. Configure retry options like maxAttempts and backoff factor directly on the task definition.

How do I schedule cron jobs with Trigger.dev?▼

Use schedules.task with a cron expression to define a scheduled task, attaching schedules declaratively or imperatively via schedules.create. Schedules support IANA timezones, externalId for multi-tenant use, and deduplicationKey for updates.

Why does triggerAndWait not return my task output directly?▼

triggerAndWait returns a Result object with ok, output, and error properties, not the raw return value. Check result.ok before accessing result.output, or call .unwrap() to throw on error and get the output directly.

Can I use Promise.all with Trigger.dev wait or trigger calls?▼

No, wrapping triggerAndWait, batchTriggerAndWait, or wait calls in Promise.all or Promise.allSettled is not supported in Trigger.dev tasks. Execute these calls sequentially within your run function instead.

How do I limit concurrency for Trigger.dev tasks?▼

Set a concurrencyLimit on a shared queue or directly on the task definition. For per-tenant control, pass a queue option with a dynamic name like user-{userId} and a concurrencyLimit when triggering the task.

What is the difference between leading and trailing debounce modes?▼

Leading mode uses the payload from the first trigger and only reschedules execution on subsequent triggers. Trailing mode uses the payload, metadata, and tags from the most recent trigger, which suits user activity and webhook bursts.