trigger-config

Configure Trigger.dev projects with trigger.config.ts and build extensions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up a Trigger.dev project requires correctly wiring build extensions for databases, browsers, media tools, and Python scripts, and misconfiguration leads to failed deployments or missing runtime dependencies. ## Core Features & Use Cases - Build Extension Setup: Configure Prisma, Playwright, Puppeteer, FFmpeg, Python, apt-get packages, and additional files in trigger.config.ts. - Deployment Customization: Set retries, machine sizes, max duration, lifecycle hooks, telemetry instrumentations, and environment variable syncing. - Use Case: When deploying a web scraping task, add the Playwright extension with Chromium and include selector files via additionalFiles so the deployed worker has everything it needs. ## Quick Start Ask the AI to configure trigger.config.ts for a Trigger.dev project that uses Prisma with migrations and Playwright with Chromium.

Frequently Asked Questions about trigger-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Prisma in a Trigger.dev project?

Add the prismaExtension from @trigger.dev/build/extensions/prisma to the build.extensions array in trigger.config.ts. Specify your schema path, set migrate to true to run migrations during build, and optionally provide directUrlEnvVarName for the direct database connection.

How to run Python scripts from Trigger.dev tasks?

Use the pythonExtension with a scripts glob, a requirementsFile, and a devPythonBinaryPath for local development. Inside tasks, call python.runScript with the script path and arguments, or python.runInline for inline code.

Playwright vs Puppeteer extension for Trigger.dev browser automation?

The Playwright extension supports chromium, firefox, and webkit browsers with a headless option, while the Puppeteer extension requires setting PUPPETEER_EXECUTABLE_PATH to a Chrome binary. Choose Playwright for multi-browser support and Puppeteer for Chrome-only workflows.

Does Trigger.dev support FFmpeg for media processing?

Yes, the ffmpeg extension from @trigger.dev/build/extensions/core installs a static FFmpeg build and automatically sets FFMPEG_PATH and FFPROBE_PATH environment variables. You can pin a version such as 7 or omit it for the Debian package.

Why do build extensions not affect local Trigger.dev development?

Build extensions only modify the deployment build, not the local dev environment. For local work you must install equivalent tools yourself, such as a local Python virtualenv or system FFmpeg, and use --log-level debug --dry-run to troubleshoot builds.