Our review
Analyzes Trigger.dev tasks, schedules, and run history to identify cost-saving opportunities such as right-sizing machines, adding maxDuration, debouncing triggers, and preventing duplicate work.
Strengths
- Combines static source analysis with live run data via MCP tools.
- References version-pinned SDK docs so recommendations match the installed SDK version.
- Covers multiple concrete levers (machine size, maxDuration, retries, queue, idempotency).
- Clear principles like free waits and aborting non-retryable errors are actionable.
Limitations
- Requires @trigger.dev/sdk installed and the MCP server for full run analysis.
- Without MCP, only static source analysis is possible; no real run data.
- Limited specifically to Trigger.dev, not general cloud cost optimization.
When asked to reduce spend or optimize costs in a project using Trigger.dev tasks, schedules, or runs.
When the project doesn't use Trigger.dev or when cost optimization requires looking beyond Trigger.dev infrastructure.
Security analysis
SafeThe skill instructs static source analysis and optional use of Trigger.dev MCP tools to inspect runs; no destructive, exfiltrating, or obfuscated actions are present. It references reading installed SDK docs and running npx for MCP setup, but only for legitimate diagnostic purposes.
No concerns found
Examples
Help me reduce my Trigger.dev bill — check my tasks and suggest cost optimizations.Audit our Trigger.dev usage and right-size the machines for our tasks.Why are we spending so much on Trigger.dev runs? Find ways to cut costs.name: trigger-cost-savings description: > Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size machines, or review task efficiency. Combines static source analysis with live run analysis via the Trigger.dev MCP tools (list_runs, get_run_details, get_current_worker). type: core library: trigger.dev
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 undernode_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-1xis right for most tasks; right-size down tasks stuck onlarge-*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.
AbortTaskRunErrorstops 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).
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.