trigger-setup

Initialize Trigger.dev projects with configuration, task directories, and environment setup.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill trigger-setup-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trigger-setup
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/.agents/skills/trigger-setup
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill trigger-setup-inventashif

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 trigger.config.ts, organizing task directories, and configuring API keys—which can be error-prone without clear guidance. ## Core Features & Use Cases - Project Initialization: Walks through installing @trigger.dev/sdk and running npx trigger.dev init to scaffold trigger.config.ts and the trigger/ directory. - Task Creation: Shows how to define and export tasks using task() or schemaTask() with unique IDs. - Environment Configuration: Covers TRIGGER_SECRET_KEY setup for development, staging, and production, plus syncing env vars into tasks. - 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 background 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.dev@latest init to generate trigger.config.ts and a trigger/ directory with a sample task. Add your project ID from the dashboard 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() or schemaTask() from @trigger.dev/sdk with a unique ID and a run function. Start the dev server with npx trigger.dev@latest dev, then trigger it from your app code or the dashboard.

Can Trigger.dev tasks live in multiple directories or a monorepo?

Yes, configure multiple directories in trigger.config.ts using the dirs array, including glob patterns like ./src/**/tasks. In monorepos, place trigger.config.ts in the package containing your tasks.

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 every task is a named export and restart the dev server after adding new tasks.

How do I use environment variables inside Trigger.dev tasks?

Tasks run on Trigger.dev infrastructure, so sync local variables using the syncEnvVars build extension in trigger.config.ts or set them in the dashboard under Project Settings. Access them in tasks via process.env.