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
- triggerdotdev/skillstheir own version, first seen Oct 19, 2026
- r2hu1/openbotstheir own version, first seen Oct 11, 2026
- adrianhajdin/ghost-aiword for word, first seen Oct 9, 2026
- Visitha2001/ghost-ai-sseword for word, first seen Jun 24, 2026
Other versions4 projects use a version of this.
Word for word · 2
- adrianhajdin/ghost-ai★ 332100% same
- Visitha2001/ghost-ai-sse★ 0100% same
Edited · 0
None found.
Wrote their own version · 2
- triggerdotdev/skills★ 35same name
- r2hu1/openbots★ 12same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- graduate-to-triggerSkill
- research-agentSkill
- research-process-builderSkill
- trigger-agentsSkill
- trigger-configSkill
- trigger-cost-savingsSkill
- trigger-realtimeSkill
- trigger-tasksSkill
- research-process-builderSkill
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
- Very specific: line 102
Create .env or set in your environment:
- Very specific: line 111
Ensure tasks are exported from files in dirs folders
- Very specific: line 112
Check trigger.config.ts points to correct directories
- Very specific: line 115
Verify project in config matches dashboard
- Very specific: line 116
Check TRIGGER_SECRET_KEY is set
- Distinctive: line 124
Add retry logic → see trigger-tasks skill
- Distinctive: line 127
Add real-time UI → see trigger-realtime skill
≈ “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.
Files
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
- Node.js 18+ or Bun
- A Trigger.dev account (https://cloud.trigger.dev)
Quick Start
1. Install the SDK
npm install @trigger.dev/sdk2. Initialize Your Project
npx trigger initThis creates:
trigger.config.ts- project configurationtrigger/directory - where your tasks livetrigger/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 dev6. 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 KeysCommon Issues
"No tasks found"
- Ensure tasks are exported from files in
dirsfolders - Check
trigger.config.tspoints to correct directories
"Project not found"
- Verify
projectin config matches dashboard - Check
TRIGGER_SECRET_KEYis set
"Task not registered"
- Restart
npx trigger devafter adding new tasks - Tasks must use
task()orschemaTask()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
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
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.

