trigger-dev-tasks — Claude Code skill: tasks and installation
trigger-dev-tasks is a Claude Code skill for building Trigger.dev background tasks and workflows. It activates for scheduled jobs, AI workflows, task hierarchies, and Zod schema validation.
Apache-2.0 ★ 16,801 updated 2026-10-29
npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a claude-codeWhat trigger-dev-tasks does
This skill guides the creation and editing of Trigger.dev tasks in TypeScript, from background processing to scheduled runs and nested workflows. It uses @trigger.dev/sdk, recommends exporting tasks and configuring retries, and shows schema validation with schemaTask and Zod.
Tasks can wait for child-task results with triggerAndWait; idempotency keys help guard actions against retries. Calls to wait.*, triggerAndWait, and batchTriggerAndWait must not be wrapped in Promise.all or Promise.allSettled. Trigger.dev tasks run on Node.js 21+ and use the @trigger.dev/sdk package.
What it helps with
- create a background task with retries
- split a workflow into subtasks
- validate task input with Zod
- set up scheduled or delayed runs
- prevent duplicate actions across retries
Example prompts for the agent
- Create a Trigger.dev task to process new orders with retries.
- Split this workflow into a parent task and subtasks.
- Add Zod validation to this task's input.
How to install trigger-dev-tasks
1Skills CLI (Vercel)
npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a claude-code2Manually: put the files in place
~/.claude/skills/trigger-dev-tasks/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/trigger-dev-tasks/
1Skills CLI (Vercel)
npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a codex2Manually: put the files in place
.agents/skills/trigger-dev-tasks/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a cursor2Manually: put the files in place
.cursor/skills/trigger-dev-tasks/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install triggerdotdev/trigger.dev .claude/skills/trigger-dev-tasks2Manually: put the files in place
.github/skills/trigger-dev-tasks/SKILL.md1Skills CLI (Vercel)
npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a gemini-cli2Platform CLI
gemini skills install https://github.com/triggerdotdev/trigger.dev --path .claude/skills/trigger-dev-tasksManually: put the files in place
.devin/skills/trigger-dev-tasks/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about trigger-dev-tasks
How do I install trigger-dev-tasks in Claude Code?
Run npx skills add triggerdotdev/trigger.dev --skill trigger-dev-tasks -a claude-code. The skill file is at ~/.claude/skills/trigger-dev-tasks/SKILL.md.
What does trigger-dev-tasks do?
It guides the implementation of Trigger.dev background tasks and workflows, including retries, schedules, subtasks, and Zod-based schema validation.
What does trigger-dev-tasks require?
Trigger.dev tasks run on Node.js 21+ and use the @trigger.dev/sdk package.
Source text
SKILL.md · Apache-2.0
---
name: trigger-dev-tasks
description: Use this skill when writing, designing, or optimizing Trigger.dev background tasks and workflows. This includes creating reliable async tasks, implementing AI workflows, setting up scheduled jobs, structuring complex task hierarchies with subtasks, configuring build extensions for tools like ffmpeg or Puppeteer/Playwright, and handling task schemas with Zod validation.
allowed-tools: Read, Write, Edit, Glob, Grep, Bash
---
# Trigger.dev Task Expert
You are an expert Trigger.dev developer specializing in building production-grade background job systems. Tasks deployed to Trigger.dev run in Node.js 21+ and use the `@trigger.dev/sdk` package.
## Critical Rules
1. **Always use `@trigger.dev/sdk`** - Never use `@trigger.dev/sdk/v3` or deprecated `client.defineJob` pattern
2. **Never use `node-fetch`** - Use the built-in `fetch` function
3. **Export all tasks** - Every task must be exported, including subtasks
4. **Never wrap wait/trigger calls in Promise.all** - `triggerAndWait`, `batchTriggerAndWait`, and `wait.*` calls cannot be wrapped in `Promise.all` or `Promise.allSettled`
## Basic Task Pattern
```ts
import { task } from "@trigger.dev/sdk";
export const processData = task({
id: "process-data",
retry: {
maxAttempts: 10,
factor: 1.8,
minTimeoutInMs: 500,
maxTimeoutInMs: 30_000,
},
run: async (payload: { userId: string; data: any[] }) => {
console.log(`Processing ${payload.data.length} items`);
return { processed: payload.data.length };
},
});
```
## Schema Task (with validation)
```ts
import { schemaTask } from "@trigger.dev/sdk";
import { z } from "zod";
export const validatedTask = schemaTask({
id: "validated-task",
schema: z.object({
name: z.string(),
email: z.string().email(),
}),
run: async (payload) => {
// Payload is automatically validated and typed
return { message: `Hello ${payload.name}` };
},
});
```
## Triggering Tasks
### From Backend Code (type-only import to prevent dependency leakage)
```ts
import { tasks } from "@trigger.dev/sdk";
import type { processData } from "./trigger/tasks";
const handle = await tasks.trigger<typeof processData>("process-data", {
userId: "123",
data: [{ id: 1 }],
});
```
### From Inside Tasks
```ts
export const parentTask = task({
id: "parent-task",
run: async (payload) => {
// Trigger and wait - returns Result object, NOT direct output
const result = await childTask.triggerAndWait({ data: "value" });
if (result.ok) {
console.log("Output:", result.output);
} else {
console.error("Failed:", result.error);
}
// Or unwrap directly (throws on error)
const output = await childTask.triggerAndWait({ data: "value" }).unwrap();
},
});
```
## Idempotency (Critical for Retries)
Always use idempotency keys when triggering tasks from inside other tasks:
```ts
import { idempotencyKeys } from "@trigger.dev/sdk";
export const paymentTask = task({
id: "process-payment",
run: async (payload: { orderId: string }) => {
// Scoped to current run - survives retries
const key = await idempotencyKeys.create(`payment-${payload.orderId}`);
await chargeCustomer.trigger(payload, {
idempotencyKey: key,
idempotencyKeyTTL: "24h",
});
},
});
```
## Trigger Options
```ts
await myTask.trigger(payload, {
delay: "1h", // Delay execution
ttl: "10m", // Cancel if not started within TTL
idempotencyKey: key,
queue: "my-queue",
machine: "large-1x", // micro, small-1x, small-2x, medium-1x, medium-2x, large-1x, large-2x
maxAttempts: 3,
tags: ["user_123"], // Max 10 tags
debounce: { // Consolidate rapid triggers
key: "unique-key",
delay: "5s",
mode: "trailing", // "leading" (default) or "trailing"
},
});
```
## Debouncing
Consolidate multiple triggers into a single execution:
```ts
// Rapid triggers with same key = single execution
await myTask.trigger({ userId: "123" }, {
debounce: {
key: "user-123-update",
delay: "5s",
},
});
// Trailing mode: use payload from LAST trigger
await myTask.trigger({ data: "latest" }, {
debounce: {
key: "my-key",
delay: "10s",
mode: "trailing",
},
});
```
Use cases: user activity updates, webhook deduplication, search indexing, notification batching.
## Batch Triggering
Up to 1,000 items per batch, 3MB per payload:
```ts
const results = await myTask.batchTriggerAndWait([
{ payload: { userId: "1" } },
{ payload: { userId: "2" } },
]);
for (const result of results) {
if (result.ok) console.log(result.output);
}
```
## Machine Presets
| Preset | vCPU | Memory |
|-------------|------|--------|
| micro | 0.25 | 0.25GB |
| small-1x | 0.5 | 0.5GB |
| small-2x | 1 | 1GB |
| medium-1x | 1 | 2GB |
| medium-2x | 2 | 4GB |
| large-1x | 4 | 8GB |
| large-2x | 8 | 16GB |
## Design Principles
1. **Break complex workflows into subtasks** that can be independently retried and made idempotent
2. **Don't over-complicate** - Sometimes `Promise.allSettled` inside a single task is better than many subtasks (each task has dedicated process and is charged by millisecond)
3. **Always configure retries** - Set appropriate `maxAttempts` based on the operation
4. **Use idempotency keys** - Especially for payment/critical operations
5. **Group related subtasks** - Keep subtasks only used by one parent in the same file, don't export them
6. **Use logger** - Log at key execution points with `logger.info()`, `logger.error()`, etc.
## Reference Documentation
For detailed documentation on specific topics, read these files:
- `basic-tasks.md` - Task basics, triggering, waits
- `advanced-tasks.md` - Tags, queues, concurrency, metadata, error handling
- `scheduled-tasks.md` - Cron schedules, declarative and imperative
- `realtime.md` - Real-time subscriptions, streams, React hooks
- `config.md` - trigger.config.ts, build extensions (Prisma, Playwright, FFmpeg, etc.)
© triggerdotdev · Apache-2.0 · triggerdotdev/trigger.dev