What problem does it solve? Trigger.dev workloads can silently accumulate unnecessary spend through oversized machines, runaway retries, missing timeouts, and over-frequent schedules. This Skill audits your tasks and run history to surface concrete cost reduction opportunities with prioritized recommendations. ## Core Features & Use Cases - Static Source Analysis: Scans task code for oversized machine presets, missing maxDuration, excessive retries, missing debounce, polling loops, and non-batched triggers. - Live Run Analysis via MCP: Uses Trigger.dev MCP tools (list_runs, get_run_details, get_current_worker) to find expensive tasks, failure patterns, and over-provisioned machines from real usage data. - Prioritized Recommendations: Produces a cost optimization report ranked by impact, with code snippets for right-sizing machines, adding debounce, and setting idempotency keys. - Use Case: Your monthly Trigger.dev bill spiked. Run this Skill to discover that an image-processing task on large-2x averages 2-second runs, and get a recommendation to switch to small-2x for roughly 16x savings on that task. ## Quick Start Analyze my Trigger.dev tasks and recent runs to find ways to reduce my monthly spend.