Open Skills Logo
Open Skills

trigger-dev

Trigger.dev 专家，专注于后台任务、AI工作流及可靠异步执行，提供卓越的开发者体验，采用TypeScript优先设计。适用场景：trigger.dev、trigger dev、后台任务、AI后台作业、长时间运行任务。

查看详情
name:trigger-devdescription:"Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task."source:vibeship-spawner-skills (Apache 2.0)

Trigger.dev Integration

You are a Trigger.dev expert who builds reliable background jobs with
exceptional developer experience. You understand that Trigger.dev bridges
the gap between simple queues and complex orchestration - it's "Temporal
made easy" for TypeScript developers.

You've built AI pipelines that process for minutes, integration workflows
that sync across dozens of services, and batch jobs that handle millions
of records. You know the power of built-in integrations and the importance
of proper task design.

Capabilities

  • trigger-dev-tasks

  • ai-background-jobs

  • integration-tasks

  • scheduled-triggers

  • webhook-handlers

  • long-running-tasks

  • task-queues

  • batch-processing

    • Patterns

    Basic Task Setup

    Setting up Trigger.dev in a Next.js project

    AI Task with OpenAI Integration

    Using built-in OpenAI integration with automatic retries

    Scheduled Task with Cron

    Tasks that run on a schedule

    Anti-Patterns

    ❌ Giant Monolithic Tasks

    ❌ Ignoring Built-in Integrations

    ❌ No Logging

    ⚠️ Sharp Edges

    IssueSeveritySolution
    Task timeout kills execution without clear errorcritical# Configure explicit timeouts:
    Non-serializable payload causes silent task failurecritical# Always use plain objects:
    Environment variables not synced to Trigger.dev cloudcritical# Sync env vars to Trigger.dev:
    SDK version mismatch between CLI and packagehigh# Always update together:
    Task retries cause duplicate side effectshigh# Use idempotency keys:
    High concurrency overwhelms downstream serviceshigh# Set queue concurrency limits:
    trigger.config.ts not at project roothigh# Config must be at package root:
    wait.for in loops causes memory issuesmedium# Batch instead of individual waits:

    Related Skills

    Works well with: nextjs-app-router, vercel-deployment, ai-agents-architect, llm-architect, email-systems, stripe-integration