name	pp-trigger-dev
description	Manage Trigger.dev background jobs, runs, schedules, and queues from the terminal
author	Mitchell Keller
license	Apache-2.0
argument-hint	<command> [args] \| install cli\|mcp
allowed-tools	Read Bash
metadata	{"openclaw":{"requires":{"bins":["trigger-dev-pp-cli"]},"install":[{"kind":"go","bins":["trigger-dev-pp-cli"],"module":"github.com/mvanhorn/printing-press-library/library/developer-tools/trigger-dev/cmd/trigger-dev-pp-cli"}]}}

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:

Install via the Printing Press installer:

npx -y @mvanhorn/printing-press install trigger-dev --cli-only

Verify: trigger-dev-pp-cli --version
Ensure $GOPATH/bin (or $HOME/go/bin) is on $PATH.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):

go install github.com/mvanhorn/printing-press-library/library/developer-tools/trigger-dev/cmd/trigger-dev-pp-cli@latest

If --version reports "command not found" after install, the install step did not put the binary on $PATH. Do not proceed with skill commands until verification succeeds.

Open-source background jobs and AI agent orchestration platform API

Command Reference

batches — Manage batches of task runs

trigger-dev-pp-cli batches create — Create a new batch
trigger-dev-pp-cli batches retrieve — Retrieve a batch by ID
trigger-dev-pp-cli batches retrieve-results — Retrieve batch results
trigger-dev-pp-cli batches stream-items — Stream items into a batch

deployments — Manage project deployments across environments

trigger-dev-pp-cli deployments get-latest — Get the latest deployment
trigger-dev-pp-cli deployments list — List all deployments
trigger-dev-pp-cli deployments promote — Promote a deployment to an environment
trigger-dev-pp-cli deployments retrieve — Retrieve a single deployment

envvars — Manage environment variables across environments

trigger-dev-pp-cli envvars create — Create a new environment variable
trigger-dev-pp-cli envvars delete — Delete an environment variable
trigger-dev-pp-cli envvars import — Import environment variables from a .env file
trigger-dev-pp-cli envvars list — List all environment variables
trigger-dev-pp-cli envvars retrieve — Retrieve a single environment variable
trigger-dev-pp-cli envvars update — Update an environment variable

query — Execute TRQL queries and access dashboards

trigger-dev-pp-cli query dashboards — List available dashboards
trigger-dev-pp-cli query execute — Execute a TRQL query against run data
trigger-dev-pp-cli query schema — Get the query schema

queues — Manage run queues and concurrency

trigger-dev-pp-cli queues concurrency-override — Override concurrency limit for a queue
trigger-dev-pp-cli queues concurrency-reset — Reset concurrency limit to default
trigger-dev-pp-cli queues list — List all queues
trigger-dev-pp-cli queues pause — Pause or resume a queue
trigger-dev-pp-cli queues retrieve — Retrieve a single queue

runs — List, inspect, and manage task runs

trigger-dev-pp-cli runs add-tags — Add tags to a run
trigger-dev-pp-cli runs cancel — Cancel a running or queued run
trigger-dev-pp-cli runs list — List runs with filtering and pagination
trigger-dev-pp-cli runs replay — Replay a failed or completed run
trigger-dev-pp-cli runs reschedule — Reschedule a delayed run
trigger-dev-pp-cli runs retrieve — Retrieve a single run by ID including payload and output
trigger-dev-pp-cli runs retrieve-events — Retrieve events for a run
trigger-dev-pp-cli runs retrieve-result — Retrieve the result/output of a completed run
trigger-dev-pp-cli runs retrieve-trace — Retrieve trace spans for a run
trigger-dev-pp-cli runs update-metadata — Update run metadata key-value pairs

schedules — Manage cron schedules for recurring tasks

trigger-dev-pp-cli schedules activate — Activate a schedule
trigger-dev-pp-cli schedules create — Create a new schedule
trigger-dev-pp-cli schedules deactivate — Deactivate a schedule
trigger-dev-pp-cli schedules delete — Delete a schedule
trigger-dev-pp-cli schedules list — List all schedules
trigger-dev-pp-cli schedules retrieve — Retrieve a single schedule
trigger-dev-pp-cli schedules timezones — List supported timezones
trigger-dev-pp-cli schedules update — Update a schedule

tasks — Trigger tasks to run in the background

trigger-dev-pp-cli tasks batch-trigger — Trigger multiple task runs in a batch
trigger-dev-pp-cli tasks trigger — Trigger a single task run
trigger-dev-pp-cli tasks trigger-batch — Trigger a pre-configured task batch

waitpoints — Manage waitpoints for human-in-the-loop workflows

trigger-dev-pp-cli waitpoints complete — Complete a waitpoint token
trigger-dev-pp-cli waitpoints complete-callback — Complete a waitpoint via HTTP callback
trigger-dev-pp-cli waitpoints create — Create a waitpoint token
trigger-dev-pp-cli waitpoints list — List all waitpoint tokens
trigger-dev-pp-cli waitpoints retrieve — Retrieve a waitpoint token

Freshness Contract

This printed CLI owns bounded freshness only for registered store-backed read command paths. In --data-source auto mode, those paths check sync_state and may run a bounded refresh before reading local data. --data-source local never refreshes. --data-source live reads the API and does not mutate the local store. Set TRIGGER_DEV_NO_AUTO_REFRESH=1 to skip the freshness hook without changing source selection.

Covered paths:

trigger-dev-pp-cli deployments
trigger-dev-pp-cli deployments get-latest
trigger-dev-pp-cli deployments list
trigger-dev-pp-cli deployments promote
trigger-dev-pp-cli deployments retrieve
trigger-dev-pp-cli envvars
trigger-dev-pp-cli envvars create
trigger-dev-pp-cli envvars delete
trigger-dev-pp-cli envvars import
trigger-dev-pp-cli envvars list
trigger-dev-pp-cli envvars retrieve
trigger-dev-pp-cli envvars update
trigger-dev-pp-cli query
trigger-dev-pp-cli query dashboards
trigger-dev-pp-cli query execute
trigger-dev-pp-cli query schema
trigger-dev-pp-cli queues
trigger-dev-pp-cli queues concurrency-override
trigger-dev-pp-cli queues concurrency-reset
trigger-dev-pp-cli queues list
trigger-dev-pp-cli queues pause
trigger-dev-pp-cli queues retrieve
trigger-dev-pp-cli runs
trigger-dev-pp-cli runs add-tags
trigger-dev-pp-cli runs cancel
trigger-dev-pp-cli runs list
trigger-dev-pp-cli runs replay
trigger-dev-pp-cli runs reschedule
trigger-dev-pp-cli runs retrieve
trigger-dev-pp-cli runs retrieve-events
trigger-dev-pp-cli runs retrieve-result
trigger-dev-pp-cli runs retrieve-trace
trigger-dev-pp-cli runs update-metadata
trigger-dev-pp-cli schedules
trigger-dev-pp-cli schedules activate
trigger-dev-pp-cli schedules create
trigger-dev-pp-cli schedules deactivate
trigger-dev-pp-cli schedules delete
trigger-dev-pp-cli schedules list
trigger-dev-pp-cli schedules retrieve
trigger-dev-pp-cli schedules timezones
trigger-dev-pp-cli schedules update
trigger-dev-pp-cli schedules-timezones
trigger-dev-pp-cli waitpoints
trigger-dev-pp-cli waitpoints complete
trigger-dev-pp-cli waitpoints complete-callback
trigger-dev-pp-cli waitpoints create
trigger-dev-pp-cli waitpoints list
trigger-dev-pp-cli waitpoints retrieve

When JSON output uses the generated provenance envelope, freshness metadata appears at meta.freshness. Treat it as current-cache freshness for the covered command path, not a guarantee of complete historical backfill or API-specific enrichment.

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

trigger-dev-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Auth Setup

Run trigger-dev-pp-cli auth setup for the URL and steps to obtain a token (add --launch to open the URL). Then store it:

trigger-dev-pp-cli auth set-token YOUR_TOKEN_HERE

Or set TRIGGER_SECRET_KEY as an environment variable.

Run trigger-dev-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

Pipeable — JSON on stdout, errors on stderr
Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
```
trigger-dev-pp-cli deployments list --agent --select id,name,status
```
Previewable — --dry-run shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Explicit retries — use --idempotent only when an already-existing create should count as success, and --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.

Agent Feedback

When you (or the agent) notice something off about this CLI, record it:

trigger-dev-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
trigger-dev-pp-cli feedback --stdin < notes.txt
trigger-dev-pp-cli feedback list --json --limit 10

Entries are stored locally at ~/.trigger-dev-pp-cli/feedback.jsonl. They are never POSTed unless TRIGGER_DEV_FEEDBACK_ENDPOINT is set AND either --send is passed or TRIGGER_DEV_FEEDBACK_AUTO_SEND=true. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

Output Delivery

Every command accepts --deliver <sink>. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Sink	Effect
`stdout`	Default; write to stdout only
`file:<path>`	Atomically write output to `<path>` (tmp + rename)
`webhook:<url>`	POST the output body to the URL (`application/json` or `application/x-ndjson` when `--compact`)

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

Named Profiles

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

trigger-dev-pp-cli profile save briefing --json
trigger-dev-pp-cli --profile briefing deployments list
trigger-dev-pp-cli profile list --json
trigger-dev-pp-cli profile show briefing
trigger-dev-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults. agent-context lists all available profiles under available_profiles so introspecting agents discover them at runtime.

Exit Codes

Code	Meaning
0	Success
2	Usage error (wrong arguments)
3	Resource not found
4	Authentication required
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

Argument Parsing

Parse $ARGUMENTS:

Empty, help, or --help → show trigger-dev-pp-cli --help output
Starts with install → ends with mcp → MCP installation; otherwise → see Prerequisites above
Anything else → Direct Use (execute as CLI command with --agent)

MCP Server Installation

Install the MCP server:

go install github.com/mvanhorn/printing-press-library/library/developer-tools/trigger-dev/cmd/trigger-dev-pp-mcp@latest

claude mcp add trigger-dev-pp-mcp -- trigger-dev-pp-mcp

Verify: claude mcp list

Direct Use

Check if installed: which trigger-dev-pp-cli If not found, offer to install (see Prerequisites at the top of this skill).
Match the user query to the best command from the Unique Capabilities and Command Reference above.

Execute with the --agent flag:

trigger-dev-pp-cli <command> [subcommand] [args] --agent

If ambiguous, drill into subcommand help: trigger-dev-pp-cli <command> --help.

name	pp-trigger-dev
description	Manage Trigger.dev background jobs, runs, schedules, and queues from the terminal
author	Mitchell Keller
license	Apache-2.0
argument-hint	<command> [args] \| install cli\|mcp
allowed-tools	Read Bash
metadata	{"openclaw":{"requires":{"bins":["trigger-dev-pp-cli"]},"install":[{"kind":"go","bins":["trigger-dev-pp-cli"],"module":"github.com/mvanhorn/printing-press-library/library/developer-tools/trigger-dev/cmd/trigger-dev-pp-cli"}]}}