Automated summary
Analyzes Trigger.dev tasks, schedules and runs to surface cost-optimization levers, pairing static source review with live run data from the Trigger.dev MCP server.
Strengths
- Combines static code analysis with real run data through the list_runs, get_run_details and get_current_worker MCP tools
- Reads guidance bundled inside the installed SDK, so recommendations match the SDK version the project actually uses
- Targets concrete levers: free waits over 5 seconds, machine presets, maxDuration caps, debouncing, idempotency keys and AbortTaskRunError
- Degrades honestly: without the MCP server it falls back to static source analysis only and never fabricates run data
Limitations
- Requires @trigger.dev/sdk to be installed, with its bundled skills/ and docs/ paths resolvable
- Live run analysis depends on installing and configuring the Trigger.dev MCP server
- Scoped to cost and efficiency, not task correctness or broader architectural redesign
Use it when you need to cut Trigger.dev spend, audit task usage or right-size machines for tasks.
Skip it when the project doesn't run on Trigger.dev, or when the issue is a task's functionality rather than its cost.
Security analysis
CautionThe skill uses legitimate package installation and MCP setup commands for Trigger.dev cost analysis. No destructive, exfiltrating, or obfuscated actions are present, but executing `npx` and installing SDK packages is a powerful operation that warrants caution.
- •Instructs running `npx trigger.dev@latest install-mcp` and `node -p "require.resolve('@trigger.dev/sdk/package.json')"`, which executes third-party code and may install packages over the network.
- •Directs the agent to install `@trigger.dev/sdk` if not present, without pinning a version in the instruction.
Examples
Review my Trigger.dev tasks and tell me where I'm overspending — check machine presets, maxDuration and retry settings.My tasks run on large-2x but usually finish in under 10 seconds. Right-size them and estimate the savings.Use the Trigger.dev MCP tools to list my recent runs and find the most expensive or runaway ones.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).
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/trigger-dev-cost-savings-analysis-mrwak97x/download' --output '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md.part' && mv '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md.part' '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md' && test -s '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/trigger-cost-savings' && cp -R '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x' '.claude/skills/trigger-cost-savings'Cursor
test -f '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md' && test -s '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/trigger-cost-savings' && cp -R '.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x' '.cursor/skills/trigger-cost-savings'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x'openskills read 'trigger-dev-cost-savings-analysis-mrwak97x'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/trigger-dev-cost-savings-analysis-mrwak97x/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.