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.