trigger-dev-tasks

Design Trigger.dev tasks and workflows with Zod validation and SDK exports.

2.0k|183|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/agentset-ai/agentset --skill trigger-dev-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trigger-dev-tasks
Source: https://github.com/agentset-ai/agentset/tree/main/.agents/skills/trigger-dev-tasks
Command: npx skills add https://github.com/agentset-ai/agentset --skill trigger-dev-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers design, implement, and optimize Trigger.dev background tasks and workflows, reducing boilerplate and ensuring best practices across complex task hierarchies.

Core Features & Use Cases

  • Task scaffolding and export discipline: ensure every task is defined with a proper run function, exported, and aligned with the @trigger.dev/sdk.
  • Subtask composition and orchestration: build reliable, retryable, and idempotent subtasks within larger automation workflows.
  • Build extensions and tool integration: structure integration points for FFmpeg, Playwright, Puppeteer, or other tooling in setup phases.
  • Validation and observability guidance: enforce schema validation (e.g., Zod) and provide guidance on logging, tracing, and metadata.

Quick Start

Create a simple Trigger.dev task skeleton with id "example-task", implement a run function that logs input and returns a summary, export the task, and include a sample trigger usage.

Frequently Asked Questions about trigger-dev-tasks

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

FAQPage Schema
How do I structure Trigger.dev tasks and subtasks for complex workflows?

Trigger.dev task orchestration uses the @trigger.dev/sdk to define and export run functions. For subtask composition, avoid Promise.all to ensure reliable retries and idempotency across complex automation workflows.

How do I integrate Playwright or FFmpeg into Trigger.dev workflows?

Integrate Playwright or FFmpeg into Trigger.dev workflows by configuring build extensions during the setup phase. This structures integration points so tooling executes reliably within your async task environment.

Does Trigger.dev support Zod schema validation for task inputs?

Trigger.dev supports Zod schema validation to enforce input shapes for async tasks. Applying Zod ensures payload consistency and provides observability guidance for logging, tracing, and metadata.

Why should I avoid Promise.all when orchestrating Trigger.dev subtasks?

Avoid Promise.all in Trigger.dev subtask orchestration because it bypasses the platform's built-in retry and tracing mechanisms. Using native task triggers instead ensures reliable, idempotent execution and proper metadata tracking.

What is the proper export discipline for Trigger.dev SDK tasks?

Proper Trigger.dev SDK task export discipline requires every task to be defined with a run function and explicitly exported. This ensures the platform correctly registers and schedules the async automation workflows.