免费在 GitHub 公开

trigger-authoring-tasks

Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts. Load this whenever you are authoring or editing code inside a /trigger directory, defining a task, or writing backend code that triggers tasks. Realtime/React hooks and AI chat are covered by separate skills.

中文简介正在准备中。当前显示原文说明。

code-with-antonio/browser-automation-app

查看安装方法

包含的文件（1）

SKILL.md3.7 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Authoring Trigger.dev Tasks

The full, version-pinned reference for authoring tasks ships inside your installed @trigger.dev/sdk. Read it before writing code — it always matches the SDK version in this project, so it never drifts:

Skill: node_modules/@trigger.dev/sdk/skills/trigger-authoring-tasks/SKILL.md — the complete guide (setup, schemaTask, retries, triggering + the Result shape, idempotency, waits, metadata, scheduled tasks, queues/concurrency, trigger.config.ts).
Docs: the full, version-pinned docs ship bundled at node_modules/@trigger.dev/sdk/docs/; the skill above lists the exact pages it draws from in its sources: frontmatter. Grep for an API, e.g. grep -rl "schemaTask" node_modules/@trigger.dev/sdk/docs/.

If those paths don't exist, @trigger.dev/sdk isn't installed yet — install it first. In a non-hoisted layout, resolve the package with node -p "require.resolve('@trigger.dev/sdk/package.json')" and read skills/ + docs/ beside it.

Always import from @trigger.dev/sdk — never @trigger.dev/sdk/v3 (deprecated alias) or @trigger.dev/core.

Common mistakes

CRITICAL: Treating the wait result as the output. triggerAndWait and wait.forToken return a Result object, not the raw output.
- Wrong: const out = await childTask.triggerAndWait(p); use(out.foo);
- Correct: const r = await childTask.triggerAndWait(p); if (r.ok) use(r.output.foo); (or .unwrap()).
Wrapping triggerAndWait / batchTriggerAndWait / wait in Promise.all.
- Wrong: await Promise.all([childTask.triggerAndWait(a), childTask.triggerAndWait(b)]);
- Correct: await childTask.batchTriggerAndWait([{ payload: a }, { payload: b }]); (or a sequential for-loop).
Importing the task instance into backend code.
- Wrong: import { emailSequence } from "~/trigger/emails"; in a route handler.
- Correct: import type { emailSequence } plus tasks.trigger<typeof emailSequence>("email-sequence", payload).
Calling metadata.set/get outside run().
- Wrong: setting metadata at module scope or in unrelated backend code (a no-op; get returns undefined).
- Correct: call inside run() or a task lifecycle hook.
Assuming child tasks inherit the parent's queue or metadata.
- Wrong: expecting a subtask to share the parent's concurrencyLimit or see its metadata.
- Correct: subtasks run on their own queue; pass metadata explicitly via { metadata: metadata.current() }, or push up with metadata.parent.*.
Bundling native/WASM packages.
- Wrong: leaving sharp, re2, sqlite3, or WASM packages in the default bundle.
- Correct: add them to build.external in trigger.config.ts.
Relying on a raw string idempotency key being global.
- Wrong: trigger(p, { idempotencyKey: "welcome-email" }) expecting once-ever (true only in v4.3.0 and earlier).
- Correct: await idempotencyKeys.create("welcome-email", { scope: "global" }).

References

Sibling skills: trigger-realtime-and-frontend (subscribe to runs, trigger from the frontend), trigger-authoring-chat-agent and trigger-chat-agent-advanced (AI chat agents).

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

clerk

免费

Clerk authentication router. Use when user asks about Clerk CLI operations, adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, React patterns, Vue patterns, Nuxt patterns, Astro patterns, TanStack Start patterns, Expo patterns, React Router patterns, Chrome Extension patterns, organizations, billing, subscriptions, payments, pricing, plans, seat-based pricing, feature entitlements, syncing users, or testing. Automatically routes to the specific skill based on their task.

中文简介正在准备中。当前显示原文说明。