trigger-setup

Initialize Trigger.dev projects with trigger.config.ts, task directories, and environment configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @trigger.dev/sdk, and includes references (resource) components.

What problem does it solve? Setting up Trigger.dev for the first time involves multiple steps—installing the SDK, creating configuration files, structuring task directories, and managing API keys—which can be error-prone without clear guidance. ## Core Features & Use Cases - Project Initialization: Walks through installing @trigger.dev/sdk, running npx trigger init, and creating trigger.config.ts with the correct project ID. - Task Creation: Shows how to define and export tasks using task() from @trigger.dev/sdk and trigger them from application code. - Environment & Structure Guidance: Reference docs cover TRIGGER_SECRET_KEY management across dev/staging/prod, monorepo layouts, multiple task directories, and collocated task patterns. - Use Case: You are adding background job processing to an existing Node.js app and need Trigger.dev configured correctly with a working first task and a running dev server. ## Quick Start Set up Trigger.dev in my project, create the trigger.config.ts file, and scaffold my first task.

Frequently Asked Questions about trigger-setup

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?▼

Install @trigger.dev/sdk via npm, then run npx trigger init to generate trigger.config.ts and a trigger/ directory with a sample task. Add your project ID from the dashboard to the config and set TRIGGER_SECRET_KEY in your environment.

How do I create my first Trigger.dev task?▼

Create a file in the trigger/ directory that exports a task using task() from @trigger.dev/sdk with a unique id and a run function. Start the dev server with npx trigger dev, then trigger it from your app code or the dashboard Test tab.

Can Trigger.dev be used in a monorepo?▼

Yes. Place trigger.config.ts in the package containing your tasks, with the trigger/ directory alongside it. You can also configure multiple task directories or glob patterns like ./src/**/tasks in the dirs array.

Why does Trigger.dev say no tasks found?▼

This happens when tasks are not exported from files in the configured dirs folders, or trigger.config.ts points to wrong directories. Ensure tasks use named exports with task() or schemaTask() and restart npx trigger dev after adding new tasks.

How do I manage Trigger.dev API keys across environments?▼

Use separate keys per environment: tr_dev_ for development, tr_stg_ for staging, and tr_prod_ for production, all from the dashboard API Keys section. Store them in .env files locally or in your CI/CD platform's secret management.