Skill

trigger-dev

Durable background jobs and AI agent orchestration — runs, schedules, deployments, batches, queues, waitpoints, env vars, and TRQL analytics

Verified: 2026-05-13 (printing-press-ingest-2026-05-13+enrich-capability-skill)

When to use trigger-dev

Choose if

You run background jobs or agents on Trigger.dev and want an agent loop that can triage incidents, debug staging-vs-prod env drift, attribute LLM cost per model/task pair, and tail failures in real time. Versus the Trigger.dev web dashboard, this exposes TRQL analytics and joinable run data through a `--compact` agent-friendly CLI with typed exit codes for self-correction.

Avoid if

You're not on Trigger.dev — this is platform-specific. Also avoid when the agent needs to deploy or write task code (use the official Trigger.dev SDK for that); this CLI is a management/analytics surface, not a task author. If you only have a public API key, payload and output fields are omitted — upgrade to a private key first.

Risk Flags

  • MEDIUM auth API keys are environment-scoped — a dev key cannot manage prod runs. The CLI returns a typed scope mismatch error when keys cross environments. Public API keys cause the API to omit payload and output fields for security; agents needing those must use a private key.
  • MEDIUM rate_limit Upstream returns HTTP 429 with `Retry-After`; the CLI's adaptive limiter honors it automatically. Batch endpoints cap at 1000 payloads with SDK 4.3.1+ (500 prior) — fan-out workloads must chunk.
  • MEDIUM data_quality Zombie crons that stop firing or whose runs all fail can go unnoticed without explicit auditing — README calls out detection as a primary agent use case. Callback-URL `callbackHash` doubles as the auth token; protect it on the agent side.
  • LOW scope Read + light-management surface over Trigger.dev's runs/schedules/deployments/ batches/queues/waitpoints/env vars/TRQL analytics. Not a replacement for writing or deploying tasks (use the official SDK for that).

Cost

Type: Free · Free tier: The CLI itself is free to install (MIT-family). It wraps the Trigger.dev API using an API key scoped per environment (dev vs prod). Trigger.dev's own pricing is not disclosed in this README — see trigger.dev for plan details.

Install

Default

go install github.com/mvanhorn/printing-press-library/library/developer-tools/trigger-dev/cmd/trigger-dev-pp-cli@latest
# Use a private (not public) API key for full payload + output visibility.
# Scope the key to the right environment — dev keys can't touch prod runs.
export TRIGGER_API_KEY=<your-key>

Setup docs →

Estimated time to first success: ~10 min

Dependencies

Minimum runtime: Go (for `go install`) or pre-built binary (macOS / Unix releases)

Distribution

Repository
https://github.com/mvanhorn/printing-press-library
License
MIT