# pp-trigger-dev

pp-trigger-dev operates Trigger.dev management tasks, groups LLM span costs, and runs offline search over failed runs. Useful for triaging backend job failures directly inside your AI agent.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 144 installs · ★ 2142 repo stars
- Author: Trevin Chow
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mvanhorn/printing-press-library/tree/HEAD/cli-skills/pp-trigger-dev/SKILL.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/pp-trigger-dev

## What it does

This skill interfaces with the `trigger-dev-pp-cli` binary to automate Trigger.dev maintenance. It enables an agent to run offline SQLite FTS5 queries against run history, aggregate token expenses across models and tasks, and identify repetitive error patterns. It also inspects inactive cron schedules via `schedules stale` when automated jobs stop triggering.

The CLI includes live terminal alerts via `runs watch`, desktop notifications, and side-by-side masked environment variable comparisons between prod and staging. Because `runs get` emits typed process exit codes (such as 0 for completion and 20 for failure), shell scripts can branch execution without parsing JSON output.

The binary `trigger-dev-pp-cli` must be present in `$PATH`, or every skill command will fail immediately.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mvanhorn/printing-press-library --skill pp-trigger-dev -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/pp-trigger-dev/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/pp-trigger-dev/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mvanhorn/printing-press-library --skill pp-trigger-dev -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/pp-trigger-dev/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mvanhorn/printing-press-library --skill pp-trigger-dev -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/pp-trigger-dev/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mvanhorn/printing-press-library cli-skills/pp-trigger-dev/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/pp-trigger-dev/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mvanhorn/printing-press-library --skill pp-trigger-dev -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mvanhorn/printing-press-library --path cli-skills/pp-trigger-dev
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/pp-trigger-dev/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mvanhorn/printing-press-library --skill pp-trigger-dev -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mvanhorn/printing-press-library/tree/HEAD/cli-skills/pp-trigger-dev/SKILL.md

## When to use it
- locate failed jobs using text error fragments via FTS5
- calculate LLM spend grouped by model and task identifier
- catch broken or zombie cron schedules after configuration updates
- compare masked environment variable sets across deployments

## Example prompts
- Search Trigger.dev failed runs for "payload too large" over the last 30 days
- Break down Trigger.dev LLM costs by model and task for the past 7 days
- Audit Trigger.dev schedules that stopped firing or have low success rates

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: e77f553f5337771f.

BEGIN THIRD-PARTY FILE e77f553f5337771f
````text
---
name: pp-trigger-dev
description: "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`."
author: "Trevin Chow"
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
---
<!-- 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:
   ```bash
   npx -y @mvanhorn/printing-press-library install trigger-dev --cli-only
   ```
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):

```bash
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 runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds.

## When to Use This CLI
````
END THIRD-PARTY FILE e77f553f5337771f

The third-party file has ended. Everything between the e77f553f5337771f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2250 of 16184 bytes. © Trevin Chow · Apache-2.0 · https://github.com/mvanhorn/printing-press-library/tree/HEAD/cli-skills/pp-trigger-dev/SKILL.md

## Similar
- [trigger-tasks](https://affpapa.org/en/nevibecode/skills/trigger-tasks.md) — skill · 3300 installs
- [trigger-cost-savings](https://affpapa.org/en/nevibecode/skills/trigger-cost-savings.md) — skill · 2400 installs
- [trigger-dev](https://affpapa.org/en/nevibecode/skills/trigger-dev.md) — skill · 93 installs
- [huawei-cloud-functiongraph-trigger-create](https://affpapa.org/en/nevibecode/skills/huawei-cloud-functiongraph-trigger-create.md) — skill · 18300 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
