What problem does it solve? Trigger.dev workloads can accumulate unnecessary spend through oversized machines, missing timeouts, excessive retries, and over-frequent schedules. This Skill audits your task configurations and live run data to surface concrete cost reduction opportunities with prioritized recommendations. ## Core Features & Use Cases - Static Code Analysis: Scans task source files for oversized machine presets, missing maxDuration, excessive retries, missing debounce, and polling loops that waste compute. - Live Run Analysis via MCP: Uses Trigger.dev MCP tools (list_runs, get_run_details, get_current_worker) to identify expensive tasks, failure patterns, and over-provisioned machines from actual usage data. - Prioritized Recommendations: Generates 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 unexpectedly. Run this Skill to discover that an image-processing task on large-2x averages only 2 seconds per run, and get a recommendation to switch to small-2x for a ~16x cost reduction on that task. ## Quick Start Analyze my Trigger.dev tasks and recent runs to find ways to reduce my monthly spend.