Brightdata Proxy
brightdata/skills
Generate working code that routes HTTP requests through Bright Data proxy networks (Datacenter, ISP, Residential, Mobile) and help users decide which network and IP pool type to use (shared pool…
Configures Trigger.dev projects through trigger.config.ts, with build extensions for Prisma, Playwright, Puppeteer, FFmpeg, Python and system packages.
Install Trigger.dev Configuration
$ npx skills add papermark/papermark --skill trigger-config -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install papermark/papermark trigger-config --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/trigger-config .claude/skills/trigger-config && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "trigger-config" agent skill from https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-config into .claude/skills/trigger-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-config", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-configType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add papermark/papermark --skill trigger-config -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install papermark/papermark trigger-config --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/trigger-config .agents/skills/trigger-config && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trigger-config" agent skill from https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-config into .agents/skills/trigger-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-config", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add papermark/papermark --skill trigger-config -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install papermark/papermark trigger-config --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/trigger-config .cursor/skills/trigger-config && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "trigger-config" agent skill from https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-config into .cursor/skills/trigger-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-config", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/papermark/papermark.git --path .agents/skills/trigger-config--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add papermark/papermark --skill trigger-config -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install papermark/papermark trigger-config --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/trigger-config .gemini/skills/trigger-config && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "trigger-config" agent skill from https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-config into .gemini/skills/trigger-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-config", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install papermark/papermark trigger-configInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add papermark/papermark --skill trigger-config -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/trigger-config .github/skills/trigger-config && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "trigger-config" agent skill from https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-config into .github/skills/trigger-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-config", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add papermark/papermark --skill trigger-config -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install papermark/papermark trigger-config --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/trigger-config .opencode/skills/trigger-config && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "trigger-config" agent skill from https://github.com/papermark/papermark/tree/main/.agents/skills/trigger-config into .opencode/skills/trigger-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-config", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
trigger-config- GitHub stars
- 9.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 123 words
- Files
- 2 (incl. references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Configures Trigger.dev projects through trigger.config.ts, with build extensions for Prisma, Playwright, Puppeteer, FFmpeg, Python and system packages.
- Works in 4 steps: Pin versions for reproducible builds → Use syncEnvVars for dynamic secrets → Add native modules to build.external array → …
- Setting up a new Trigger.dev project
- SKILL.md covers When to Use, Basic Configuration, Common Build Extensions and Common Extension Combinations, plus 4 more sections
- Needs API_KEY
What it does
The skill covers the trigger.config.ts file that defines a Trigger.dev project and its build extensions. It shows the basic defineConfig setup and then extension snippets for database support with Prisma, browser automation with Playwright or Puppeteer, media processing with FFmpeg, Python scripts run from tasks, apt-get system packages, additional files, and syncing environment variables.
Combinations are given for common cases: a full-stack web app (Prisma with migrations plus additional files), AI and ML processing through the Python extension, and web scraping with Playwright. It also touches global lifecycle hooks such as onStartAttempt, the default machine size and telemetry integration, with a longer reference in references/config.md.
When your agent uses it
- Setting up a new Trigger.dev project
- Adding Prisma or TypeORM support to Trigger.dev tasks
- Running Playwright, Puppeteer or FFmpeg inside Trigger.dev tasks
- Installing system packages or syncing environment variables for deployments
Example prompts
- “Add the Prisma build extension to our trigger.config.ts and run migrations on deploy.”
- “Configure Trigger.dev so tasks can run Playwright with Chromium.”
- “Make the Python scripts under ./ai runnable from Trigger.dev tasks.”
Requirements
- A Trigger.dev project using @trigger.dev/sdk
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Pin versions for reproducible builds
- Use syncEnvVars for dynamic secrets
- Add native modules to build.external array
- Debug with --log-level debug --dry-run
What it can do on your machine
Read from SKILL.md and the folder at commit ed19717. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Trigger.dev Configuration loads about 1.2k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 46 tokens; SKILL.md has 123 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 123 words (~1,176 tokens).
“Configure your Trigger.dev project with trigger.config.ts and build extensions.”
- name
- trigger-config
Files
SKILL.md and 1 other file (references) in .agents/skills/trigger-config of papermark/papermark.
- SKILL.md
- references/config.md
Open the folder on GitHubat commit ed19717
Compare with similar skills
Trigger.dev Configuration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Trigger.dev Configuration this skillpapermark/papermark | 9.2k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Brightdata Proxybrightdata/skills | 264 | — | ~5.1k | Automated safety check: Pass | MIT | |
| Monitor With HaolemeHaolemeApp/Haoleme | 157 | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Abx DlArchiveBox/abx-dl | 145 | — | ~557 | Automated safety check: Pass | MIT | |
| Code Engine SpecialistIBM/CodeEngine | 117 | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Database Migrationdavila7/claude-code-templates | 32k | 11 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Monitor With Haoleme
HaolemeApp/Haoleme
Selectively monitor important long-running or resource-intensive commands with Haoleme by prefixing them with hao, so status, output, and completion notifications sync to the mobile app.
Abx Dl
ArchiveBox/abx-dl
Use this when working on the standalone ArchiveBox downloader CLI, extractor orchestration, plugin execution, config, and output verification.
- Official
Code Engine Specialist
IBM/CodeEngine
Deploys, configures, and troubleshoots IBM Cloud Code Engine workloads using the ibmcloud ce CLI.
Database Migration
davila7/claude-code-templates
Master database schema and data migrations across ORMs (Sequelize, TypeORM, Prisma), including rollback strategies and zero-downtime deployments.
Browser Video Recording
nirholas/three.ws
Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography…
More from papermark/papermark
Trigger.dev Agent Patterns
papermark/papermark
Patterns for building LLM agents on Trigger.dev tasks: prompt chaining, routing, parallel workers, orchestrator-workers, evaluator loops and human approval gates.
Trigger.dev Cost Savings Audit
papermark/papermark
Audits Trigger.dev tasks, schedules and run history for wasteful machine sizes, retries, polling and cron frequency to cut spend.
Trigger.dev Realtime
papermark/papermark
Shows how to subscribe to Trigger.dev task runs from the backend and from React for progress indicators, live dashboards, AI response streams and approval waits.
Trigger.dev Background Tasks
papermark/papermark
Guides building durable background tasks, scheduled jobs and queues with Trigger.dev, including retries, waits, idempotency and concurrency limits.
GitHub CLI Reference
papermark/papermark
Reference for the gh command line tool covering repositories, issues, pull requests, Actions, releases, gists and codespaces, with install and login steps.
Related
Categories
Questions about Trigger.dev Configuration
What does Trigger.dev Configuration do?
Configures Trigger.dev projects through trigger.config.ts, with build extensions for Prisma, Playwright, Puppeteer, FFmpeg, Python and system packages. dev project and its build extensions. It shows the basic defineConfig setup and then extension snippets for database support with Prisma, browser automation with Playwright or Puppeteer, media processing with FFmpeg, Python scripts run from tasks, apt-get system packages, additional files, and syncing environment variables.
When should I use Trigger.dev Configuration?
Trigger.dev Configuration fits situations like: setting up a new Trigger.dev project; adding Prisma or TypeORM support to Trigger.dev tasks; running Playwright, Puppeteer or FFmpeg inside Trigger.dev tasks; installing system packages or syncing environment variables for deployments.
How do I install Trigger.dev Configuration in Claude Code?
Run `npx skills add papermark/papermark --skill trigger-config -a claude-code`. Or copy the skill folder (.agents/skills/trigger-config in papermark/papermark) into .claude/skills/trigger-config in your project. Claude Code loads it when a task matches its description.
How do I install Trigger.dev Configuration in Codex?
Run `npx skills add papermark/papermark --skill trigger-config -a codex`. Or copy the skill folder (.agents/skills/trigger-config in papermark/papermark) into .agents/skills/trigger-config in your project. Codex loads it when a task matches its description.
Can I use Trigger.dev Configuration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add papermark/papermark --skill trigger-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trigger-config, .gemini/skills/trigger-config, .github/skills/trigger-config and .opencode/skills/trigger-config in your project.
What does Trigger.dev Configuration need to run?
Going by SKILL.md and its folder, Trigger.dev Configuration needs credentials named API_KEY. Our summary lists: A Trigger.dev project using @trigger.dev/sdk.
Does Trigger.dev Configuration access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Trigger.dev Configuration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Trigger.dev Configuration use?
Trigger.dev Configuration has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Trigger.dev Configuration use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.
What are the alternatives to Trigger.dev Configuration?
Skills that share tags, products or a category with Trigger.dev Configuration: Brightdata Proxy (brightdata/skills, 264 stars), Monitor With Haoleme (HaolemeApp/Haoleme, 157 stars), Abx Dl (ArchiveBox/abx-dl, 145 stars) and Code Engine Specialist (IBM/CodeEngine, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trigger.dev Configuration?
papermark (a GitHub organization) maintains it in papermark/papermark, which has 9,242 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 28, 2026.
Source: papermark/papermark on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.