New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Trigger.dev Cost Savings Audit

by papermark in papermark/papermark

Audits Trigger.dev tasks, schedules and run history for wasteful machine sizes, retries, polling and cron frequency to cut spend.

Custom licenceAuto-check passedDevOps & Cloud

Install Trigger.dev Cost Savings Audit

skills CLI
$ npx skills add papermark/papermark --skill trigger-cost-savings -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install papermark/papermark trigger-cost-savings --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/papermark/papermark.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/trigger-cost-savings .claude/skills/trigger-cost-savings && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
trigger-cost-savings
GitHub stars
9.2k
Token cost
~1.3k tokens
SKILL.md length
399 words
Files
2 (incl. references)
Skills in repo
6
Repo updated
First seen
Licence
Custom licence

At a glance

Audits Trigger.dev tasks, schedules and run history for wasteful machine sizes, retries, polling and cron frequency to cut spend.

  • Works in 3 steps: Static Analysis (source code) → Run Analysis (requires MCP tools) → Generate Recommendations
  • Reducing the monthly bill for a project that runs Trigger.dev background tasks
  • SKILL.md covers Prerequisites: MCP Tools and Analysis Workflow
  • Calls npx; reaches trigger.dev

What it does

The agent first checks that the Trigger.dev MCP server is connected, since live run analysis relies on its list_runs, get_run_details and get_current_worker tools. Without them it tells you how to install the server and limits itself to reading source code. Before making recommendations it fetches current cost guidance from Trigger.dev's documentation, falling back to a bundled cost-reduction reference if that fails.

The static pass scans task files for nine kinds of waste: oversized machines such as large-1x or large-2x, missing maxDuration, excessive retry counts, missing debounce or idempotency keys, polling loops where waits belong, very short waits, sequential calls that could be batched, and crons that run more often than needed. The run pass then examines real usage, flagging tasks with high total compute time or high failure rates.

When your agent uses it

  • Reducing the monthly bill for a project that runs Trigger.dev background tasks
  • Right-sizing machines for tasks that rarely need a large instance
  • Reviewing task configuration for runaway-cost risks before a release
  • Finding crons that run more often than the work requires

Example prompts

  • “Audit our Trigger.dev tasks and tell me where we are overspending.”
  • “Which tasks had the worst failure rate over the last week, and are their retries wasting compute?”
  • “Check whether any task in this repo could run on a smaller machine.”

Requirements

  • The Trigger.dev MCP server, for run analysis
  • Network access to fetch Trigger.dev documentation

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Static Analysis (source code)
  2. Run Analysis (requires MCP tools)
  3. Generate Recommendations

What it can do on your machine

Read from SKILL.md and the folder at commit ed19717. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • trigger.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Trigger.dev Cost Savings Audit loads about 1.3k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 399 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 399 words (~1,348 tokens).

“Analyze task runs and configurations to find cost reduction opportunities.”

— opening of SKILL.md by papermark, Custom licence
name
trigger-cost-savings

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .agents/skills/trigger-cost-savings of papermark/papermark.

  • SKILL.md
  • references/cost-reduction.md

Open the folder on GitHubat commit ed19717

Compare with similar skills

Trigger.dev Cost Savings Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Trigger.dev Cost Savings Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Trigger.dev Cost Savings Audit this skillpapermark/papermark9.2k—~1.3kAutomated safety check: PassCustom licence
Spotinfoalexei-led/spotinfo164—~1.8kAutomated safety check: PassApache-2.0
AWS Cost Operationszxkane/aws-skills367—~2.4kAutomated safety check: PassMIT
Gram Temporalspeakeasy-api/gram273—~2.6kAutomated safety check: PassAGPL-3.0
Eks Cost Intelligenceaws-samples/appmod-blueprints115—~3.8kAutomated safety check: WarnMIT-0
Docs Tooling Notionlangchain-ai/docs426—~1.7kAutomated safety check: PassMIT

Similar skills

  • Spotinfo

    alexei-led/spotinfo

    Query Spot/preemptible VM prices, savings and interruption risk across AWS, GCP and Azure with the spotinfo CLI.

    164 GitHub stars~1.8k tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

  • AWS Cost Operations

    zxkane/aws-skills

    AWS cost optimization, monitoring, and operational excellence expert.

    367 GitHub stars~2.4k tokensUpdated 3 mo ago
    DevOps & CloudAuto-check passed

  • Gram Temporal

    speakeasy-api/gram

    A skill your agent uses when adding or changing background work in gram — a Temporal workflow, activity, schedule, signal, or ContinueAsNew loop; anything reacting to chat messages, tool calls, MCP…

    273 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Eks Cost Intelligence

    aws-samples/appmod-blueprints

    Official

    Run a live EKS cluster cost efficiency assessment — analyze spending across 6 dimensions (compute efficiency, Spot/Graviton adoption, networking, storage, observability, idle resources), calculate a…

    115 GitHub stars~3.8k tokensUpdated yesterday
    DevOps & CloudAuto-check: warnings

  • Docs Tooling Notion

    langchain-ai/docs

    Official

    Document new or changed docs-team tooling on the Notion tooling pages.

    426 GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Databricks Cost Leak Hunter

    jeremylongshore/tons-of-skills-marketplace

    Hunt down Databricks cost leaks — wasted DBUs, idle clusters, oversized SQL warehouses, and untagged runaway spend — and produce a FinOps cost report.

    2.8k GitHub stars~4.6k tokensUpdated today
    DevOps & CloudAuto-check passed

More from papermark/papermark

  • Trigger.dev Agent Patterns

    papermark/papermark

    Patterns for building LLM agents on Trigger.dev tasks: prompt chaining, routing, parallel workers, orchestrator-workers, evaluator loops and human approval gates.

    9.2k GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Trigger.dev Configuration

    papermark/papermark

    Configures Trigger.dev projects through trigger.config.ts, with build extensions for Prisma, Playwright, Puppeteer, FFmpeg, Python and system packages.

    9.2k GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Trigger.dev Realtime

    papermark/papermark

    Shows how to subscribe to Trigger.dev task runs from the backend and from React for progress indicators, live dashboards, AI response streams and approval waits.

    9.2k GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Trigger.dev Background Tasks

    papermark/papermark

    Guides building durable background tasks, scheduled jobs and queues with Trigger.dev, including retries, waits, idempotency and concurrency limits.

    9.2k GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • GitHub CLI Reference

    papermark/papermark

    Reference for the gh command line tool covering repositories, issues, pull requests, Actions, releases, gists and codespaces, with install and login steps.

    9.2k GitHub starsUsed in 3 repos~9.8k tokens
    Auto-check: warnings

Works with

Categories

Questions about Trigger.dev Cost Savings Audit

What does Trigger.dev Cost Savings Audit do?

Audits Trigger.dev tasks, schedules and run history for wasteful machine sizes, retries, polling and cron frequency to cut spend. dev MCP server is connected, since live run analysis relies on its list_runs, get_run_details and get_current_worker tools. Without them it tells you how to install the server and limits itself to reading source code.

When should I use Trigger.dev Cost Savings Audit?

Trigger.dev Cost Savings Audit fits situations like: reducing the monthly bill for a project that runs Trigger.dev background tasks; right-sizing machines for tasks that rarely need a large instance; reviewing task configuration for runaway-cost risks before a release; finding crons that run more often than the work requires.

How do I install Trigger.dev Cost Savings Audit in Claude Code?

Run `npx skills add papermark/papermark --skill trigger-cost-savings -a claude-code`. Or copy the skill folder (.agents/skills/trigger-cost-savings in papermark/papermark) into .claude/skills/trigger-cost-savings in your project. Claude Code loads it when a task matches its description.

How do I install Trigger.dev Cost Savings Audit in Codex?

Run `npx skills add papermark/papermark --skill trigger-cost-savings -a codex`. Or copy the skill folder (.agents/skills/trigger-cost-savings in papermark/papermark) into .agents/skills/trigger-cost-savings in your project. Codex loads it when a task matches its description.

Can I use Trigger.dev Cost Savings Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add papermark/papermark --skill trigger-cost-savings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trigger-cost-savings, .gemini/skills/trigger-cost-savings, .github/skills/trigger-cost-savings and .opencode/skills/trigger-cost-savings in your project.

What does Trigger.dev Cost Savings Audit need to run?

Going by SKILL.md and its folder, Trigger.dev Cost Savings Audit needs the command-line tools its instructions call (npx). Our summary lists: The Trigger.dev MCP server, for run analysis; Network access to fetch Trigger.dev documentation.

Does Trigger.dev Cost Savings Audit access the network?

SKILL.md names 1 domain. In commands or code: trigger.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Trigger.dev Cost Savings Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Trigger.dev Cost Savings Audit use?

Trigger.dev Cost Savings Audit has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Trigger.dev Cost Savings Audit use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Trigger.dev Cost Savings Audit?

Skills that share tags, products or a category with Trigger.dev Cost Savings Audit: Spotinfo (alexei-led/spotinfo, 164 stars), AWS Cost Operations (zxkane/aws-skills, 367 stars), Gram Temporal (speakeasy-api/gram, 273 stars) and Eks Cost Intelligence (aws-samples/appmod-blueprints, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Trigger.dev Cost Savings Audit?

papermark (a GitHub organization) maintains it in papermark/papermark, which has 9,243 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on August 28, 2026.

Source: papermark/papermark on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.