trigger-getting-started

Bootstrap Trigger.dev into an existing project with CLI setup, config, and a first task.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/paramcodes/autobro --skill trigger-getting-started-paramcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trigger-getting-started
Source: https://github.com/paramcodes/autobro/tree/main/.cursor/skills/trigger-getting-started
Command: npx skills add https://github.com/paramcodes/autobro --skill trigger-getting-started-paramcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @trigger.dev/sdk, @trigger.dev/build.

What problem does it solve? Setting up Trigger.dev from scratch involves many error-prone steps: authenticating the CLI, installing the right SDK versions, writing trigger.config.ts, scaffolding a tasks directory, wiring tsconfig and .gitignore, and configuring environment keys. This Skill walks an AI agent through the entire bootstrap process so a project goes from zero to a running dev server with a registered task. ## Core Features & Use Cases - Guided CLI or manual setup: Prefers the npx trigger.dev@latest init wizard, with full manual fallback steps for monorepos, existing configs, or non-interactive environments. - Human handoff handling: Identifies the two steps that require a person (CLI login and dashboard API key/project ref) and instructs the agent to pause and ask the user. - First task scaffolding: Creates a /trigger directory with an exported task(), wires trigger.config.ts, tsconfig, .gitignore, and TRIGGER_SECRET_KEY, then runs trigger dev. - Use Case: A developer says "add Trigger.dev to my Next.js app" — the agent installs @trigger.dev/sdk and @trigger.dev/build, writes the config with the project ref, scaffolds a hello-world task, and starts the dev server. ## Quick Start Ask the agent to set up Trigger.dev in this project and get a first task running in the dashboard.

Frequently Asked Questions about trigger-getting-started

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

FAQPage Schema
How do I set up Trigger.dev in an existing project?▼

Run `npx trigger.dev@latest init` for the interactive wizard, or manually install @trigger.dev/sdk and @trigger.dev/build, create a trigger.config.ts with your project ref and task dirs, add an exported task, and run `npx trigger.dev@latest dev`.

How to trigger a Trigger.dev task from my backend code?▼

Use `tasks.trigger()` from @trigger.dev/sdk with a type-only import of your task, triggering by id rather than importing the task object. Set TRIGGER_SECRET_KEY in the environment where the triggering code runs.

Does Trigger.dev work in a monorepo or Turborepo?▼

Yes, two layouts are supported: tasks in a shared package with its own trigger.config.ts consumed via workspace:*, or Trigger.dev installed directly in the app. Run `trigger dev` from the directory holding trigger.config.ts.

Why is my Trigger.dev task not showing up in the dashboard?▼

Tasks must be named exports of `task()` inside a directory listed in the config's `dirs` field, with a project-unique id. Also verify the dev server is running and the CLI and SDK versions match.

Can Trigger.dev CLI login be automated by an agent?▼

No, `trigger login` opens a browser for interactive sign-in and cannot be completed headlessly. The user must log in and create a named Development environment API key with Trigger only access from the dashboard.