trigger-dev
Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design.
Profile →npx skills add sickn33/agentic-awesome-skills --skill trigger-dev --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Describes a Trigger.dev integration that enables background tasks, AI-powered jobs, and durable, concurrent, and schedulable workflows. It targets TypeScript-first design and provides patterns for basic task setup, AI tasks with OpenAI integration, scheduled tasks with cron, batch processing, and webhook handling. It emphasizes logging, retry strategies, idempotency, and environment consistency across local and cloud runs.
How it works
- Defines a collection of capabilities such as trigger-dev-tasks, ai-background-jobs, integration-tasks, scheduled-triggers, webhook-handlers, long-running-tasks, task-queues, and batch-processing.
- Outlines core tooling like trigger-dev-sdk and trigger-cli, plus framework integrations (Next.js, Remix, Express, Hono) and several third-party integrations (OpenAI, Anthropic, Resend, Stripe, Slack, Supabase).
- Provides concrete code examples showing:
- Basic task setup with trigger.dev SDK, including id, run function, and invocation from the app (trigger, handle.wait).
- AI tasks using OpenAI integration with automatic retries.
- Scheduled tasks with cron expressions and run logic.
- Batch processing with queueing and concurrency controls.
- Webhook handling with idempotency keys to prevent duplicate processing.
- Describes patterns for handling long-running tasks, retries, and deduplication, including explicit timeout guidance and concurrency recommendations.
- Includes troubleshooting sections under "Sharp Edges" for timeouts, non-serializable payloads, environment variable syncing, SDK/CLI version mismatches, and concurrency issues, with recommended fixes and code examples.
- Demonstrates idempotency, env var synchronization, and version coherence as best practices.
When to use it
- Use for starting Trigger.dev in projects with background jobs, AI workflows, and scheduled tasks.
- Apply in scenarios requiring durable state across crashes/restarts, built-in retry, and reliable webhook processing.
- Suitable when using TS-first design and a developer-friendly UX with logging and monitoring.
What it can touch
- Core: trigger-dev-sdk, trigger-cli, and related code in a TS/Node environment.
- Frameworks: nextjs, remix, express, hono.
- Integrations: openai, anthropic, resend, stripe, slack, supabase.
- Deployment: trigger-cloud, self-hosted, docker.
- Patterns show usage examples touching trigger.config.ts, task files (e.g., src/trigger/tasks.ts), and various Trigger.dev APIs (task, schedules, idempotencyKeys, logger, wait).
Caveats
- Declared risk: critical
- Potential pitfalls include task timeouts, non-serializable payloads, environment variable synchronization challenges across Trigger.dev cloud and host deployments, and concurrency-induced rate limits on downstream services.
- Provides explicit solutions like setting machine presets, converting payloads to plain JSON-friendly structures, and employing idempotency keys.
- No guarantees of outcomes; only described behaviors and recommended fixes are provided.
# Trigger.dev Integration Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. ## Principles - Tasks are the building blocks - each task is independently retryable - Runs are durable - state survives crashes and restarts - Integrations are first-class - use built-in API wrappers for reliability - Logs are your debugging lifeline - log liberally in tasks - Concurrency protects your resources - always set limits - Delays and schedules are built-in - no external cron needed - AI-ready by design - long-running AI tasks just work - Local development matches production - use the CLI ## Capabilities - trigger-dev-tasks - ai-background-jobs - integration-tasks - scheduled-triggers - webhook-handlers - long-running-tasks - task-queues - batch-processing ## Scope - redis-queues -> bullmq-specialist - pure-event-driven -> inngest - workflow-orchestration -> temporal-craftsman - infrastructure -> infra-architect ## Tooling ### Core - trigger-dev-sdk - trigger-cli ### Frameworks - nextjs - remix - express - hono ### Integrations - openai - anthropic - resend - stripe - slack - supabase ### Deployment
- Principles
- Capabilities
- Scope
- Tooling
- Core
- Frameworks
- Integrations
- Deployment
- Patterns
- Basic Task Setup
- AI Task with OpenAI Integration
- Scheduled Task with Cron
- Batch Processing
- Webhook Handler
Create .env.trigger file Push to Trigger.dev npx trigger.dev@latest env push Update both SDK and CLI npm install @trigger.dev/sdk@latest npx trigger.dev@latest dev Or pin to same version npm install @trigger.dev/sdk@3.3.0 npx trigger.dev@3.3.0 dev npx trigger.dev@latest --version
What does the trigger-dev skill do?
Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill trigger-dev --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.