Agent skill · software engineering · mvanhorn
pp-trigger-dev
Every Trigger.dev management endpoint, plus offline FTS over runs, span-cost rollups, and zombie-schedule detection no other tool gives you. Trigger phrases: `trigger.dev failed runs`, `trigger.dev cost rollup`, `trigger.dev schedule health`, `audit trigger.dev env vars`, `watch trigger.dev failures`, `use trigger-dev`, `run trigger-dev`.
Why this skill is useful
Adds a CLI tool with unique commands for managing Trigger.dev that aren't available in public documentation, including real-time alerting and cost analysis.
What it needs
Requires trigger-dev-pp-cli installed locally. About 9k tokens when loaded. Last updated 2026-08-06. 1,890 stars on the source repository.
What this skill does
<!-- GENERATED FILE — DO NOT EDIT. This file is a verbatim mirror of library/developer-tools/trigger-dev/SKILL.md, regenerated post-merge by tools/generate-skills/. Hand-edits here are silently overwritten on the next regen. Edit the library/ source instead. See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". --> Trigger.dev — Printing Press CLI Prerequisites: Install the CLI This skill drives the trigger-dev-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows: 2. Verify: trigger-dev-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill. If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer): If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds. When to Use This CLI Reach for this CLI when an agent task needs to operate Trigger.dev programmatically: triaging failed runs, auditing schedule health, diffing env vars across environments, computing LLM costs across runs, or watching for new failures. It complements the official trigger.dev CLI (which focuses on dev-time deploy/init/dev) by exposing the management API surface as scriptable, agent-native commands with offline FTS and typed exit codes. Unique Capabilities These capabilities aren't available in any other tool for this API. Real-time terminal alerting runs watch — Watches runs for new failures and interrupts your terminal the moment one happens — desktop notification, sound, and a non-zero exit so it composes with shell loops. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/pp-trigger-dev