agentleFS
LeadGrowGTMLeadGrowGTM/research-process-builder/.agents/skills/trigger-setup/SKILL.md

trigger-setup

Skill70 starsChanged 2 months agoMITView on GitHub

Set up Trigger.dev in your project. Use when adding Trigger.dev for the first time, creating trigger.config.ts, or initializing the trigger directory.

  • Reads credentials
  • Installs packages

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create .env or set in your environment:

    line 102
  2. Very specific:

    Ensure tasks are exported from files in dirs folders

    line 111
  3. Very specific:

    Check trigger.config.ts points to correct directories

    line 112
  4. Very specific:

    Verify project in config matches dashboard

    line 115
  5. Very specific:

    Check TRIGGER_SECRET_KEY is set

    line 116
  6. Distinctive:

    Add retry logic → see trigger-tasks skill

    line 124
  7. Distinctive:

    Add real-time UI → see trigger-realtime skill

    line 127

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Trigger.dev Setup

Get Trigger.dev running in your project in minutes.

When to Use

  • Adding Trigger.dev to an existing project
  • Creating your first task
  • Setting up trigger.config.ts
  • Connecting to Trigger.dev cloud

Prerequisites

Quick Start

1. Install the SDK

npm install @trigger.dev/sdk

2. Initialize Your Project

npx trigger init

This creates:

  • trigger.config.ts - project configuration
  • trigger/ directory - where your tasks live
  • trigger/example.ts - a sample task

3. Configure trigger.config.ts

import { defineConfig } from "@trigger.dev/sdk";

export default defineConfig({
  project: "proj_xxxxx", // From dashboard
  dirs: ["./trigger"],
});

4. Create Your First Task

// trigger/my-task.ts
import { task } from "@trigger.dev/sdk";

export const myFirstTask = task({
  id: "my-first-task",
  run: async (payload: { name: string }) => {
    console.log(`Hello, ${payload.name}!`);
    return { message: `Processed ${payload.name}` };
  },
});

5. Start Development Server

npx trigger dev

6. Trigger Your Task

From your app code:

import { tasks } from "@trigger.dev/sdk";
import type { myFirstTask } from "./trigger/my-task";

await tasks.trigger<typeof myFirstTask>("my-first-task", {
  name: "World",
});

Or from the Trigger.dev dashboard "Test" tab.

Project Structure

your-project/
├── trigger.config.ts    # Required - project config
├── trigger/             # Required - task files
│   ├── my-task.ts
│   └── another-task.ts
├── package.json
└── ...

Environment Variables

Create .env or set in your environment:

TRIGGER_SECRET_KEY=tr_dev_xxxxx  # From dashboard > API Keys

Common Issues

"No tasks found"

  • Ensure tasks are exported from files in dirs folders
  • Check trigger.config.ts points to correct directories

"Project not found"

  • Verify project in config matches dashboard
  • Check TRIGGER_SECRET_KEY is set

"Task not registered"

  • Restart npx trigger dev after adding new tasks
  • Tasks must use task() or schemaTask() from @trigger.dev/sdk

Next Steps

  • Add retry logic → see trigger-tasks skill
  • Configure build extensions → see trigger-config skill
  • Build AI workflows → see trigger-agents skill
  • Add real-time UI → see trigger-realtime skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.