trigger-cost-savings

Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size…

npx skills add https://github.com/triggerdotdev/trigger.dev --skill trigger-cost-savings

Trigger.dev Cost Savings Analysis

The full, version-pinned cost-audit workflow ships inside your installed @trigger.dev/sdk. Read it before giving recommendations so they match the SDK version in this project:

  • Skill: node_modules/@trigger.dev/sdk/skills/trigger-cost-savings/SKILL.md — the static-analysis checklist, the MCP run-analysis steps (list_runs, get_run_details, get_current_worker), the report format, and the machine-preset cost table.
  • Docs: the canonical guidance is bundled at node_modules/@trigger.dev/sdk/docs/how-to-reduce-your-spend.mdx, with supporting pages under node_modules/@trigger.dev/sdk/docs/ (machines.mdx, runs/max-duration.mdx, queue-concurrency.mdx, idempotency.mdx, triggering.mdx, errors-retrying.mdx).

If those paths don't exist, @trigger.dev/sdk isn't installed yet — install it first. In a non-hoisted layout, resolve the package with node -p "require.resolve('@trigger.dev/sdk/package.json')" and read skills/ + docs/ beside it.

Live run analysis needs the Trigger.dev MCP server (npx trigger.dev@latest install-mcp). Without it, do the static source analysis only — never fabricate run data.

Key principles

  • Waits > 5 seconds are free — checkpointed, no compute charge.
  • Start small, scale up — the default small-1x is right for most tasks; right-size down tasks stuck on large-* with short durations.
  • I/O-bound tasks don't need big machines — API calls and DB queries wait on the network.
  • Add maxDuration — cap runaway compute.
  • Debounce high-frequency triggers — consolidate bursts into single runs.
  • Idempotency keys prevent duplicate billed work.
  • AbortTaskRunError stops wasteful retries — don't pay to retry permanent failures.

References

Sibling skills: trigger-authoring-tasks (the task options these levers tune: machine, maxDuration, retry, queue, idempotency), trigger-realtime-and-frontend, trigger-authoring-chat-agent and trigger-chat-agent-advanced (AI agents).

More skills from triggerdotdev

trigger-dev-tasks
triggerdotdev
Use this skill when writing, designing, or optimizing Trigger.dev background tasks and workflows. This includes creating reliable async tasks, implementing AI…
official
trigger-authoring-chat-agent
triggerdotdev
Author and run a durable AI chat agent with chat.agent from @trigger.dev/sdk/ai: the per-turn run loop, why you MUST spread ...chat.toStreamTextOptions()…
official
trigger-agents
triggerdotdev
AI agent patterns with Trigger.dev - orchestration, parallelization, routing, evaluator-optimizer, and human-in-the-loop. Use when building LLM-powered tasks…
official
trigger-config
triggerdotdev
Configure Trigger.dev projects with trigger.config.ts. Use when setting up build extensions for Prisma, Playwright, FFmpeg, Python, or customizing deployment…
official
trigger-cost-savings
triggerdotdev
Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size…
official
trigger-realtime
triggerdotdev
Subscribe to Trigger.dev task runs in real-time from frontend and backend. Use when building progress indicators, live dashboards, streaming AI/LLM responses,…
official
trigger-setup
triggerdotdev
Set up Trigger.dev in your project. Use when adding Trigger.dev for the first time, creating trigger.config.ts, or initializing the trigger directory.
official
trigger-tasks
triggerdotdev
Build AI agents, workflows and durable background tasks with Trigger.dev. Use when creating tasks, triggering jobs, handling retries, scheduling cron jobs, or…
official