Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size mach
复制下面这句话,粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具,它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-trigger-cost-savings-e8f567951ce2 ,按照其中的说明把「trigger-cost-savings」安装到你(当前 AI 工具)中。执行前先告诉我将运行的命令和写入的位置,等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件,由原作者维护。在 GitHub 查看
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:
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.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.
small-1x is right for most tasks; right-size down tasks stuck on large-* with short durations.maxDuration — cap runaway compute.AbortTaskRunError stops wasteful retries — don't pay to retry permanent failures.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).