CtrlK
BlogDocsLog inGet started
Tessl Logo

cost-optimizer

Trigger when the user asks to audit Claude Code costs, reduce token spend, says "my Claude bill is too high", "optimize my CLAUDE.md", "why is this project burning tokens", or "/cost-optimizer". Scans a project for the common Claude Code cost leaks and returns a prioritized fix list.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and token-efficient, with executable checks and a concrete output template. The main gap is the absence of an explicit validation/reconciliation step before emitting the ranked report, which caps workflow clarity.

Suggestions

Add an explicit checkpoint step after running all checks — e.g. 'Before output, re-verify every FAIL against the command output and drop any check that did not actually fail' — to create a validate→fix→retry feedback loop.

State the aggregation rule that turns per-check PASS/WARN/FAIL into the Priority 1/2/3 ranking, so the ranking is deterministic rather than implied.

Note the destructive-operations caveat: model-pinning and hook fixes it recommends can change behavior, so suggest the user confirm before editing .claude/settings.json or skill files.

DimensionReasoningScore

Conciseness

Lean and directive throughout — checks are given as executable shell snippets with terse PASS/WARN/FAIL thresholds and one-line fixes, assuming Claude's competence without restating basics like what a prompt cache is.

3 / 3

Actionability

Each check provides copy-paste-ready commands (wc -l, find, grep, du -sh) with explicit numeric thresholds and concrete fixes, plus a concrete ranked output template.

3 / 3

Workflow Clarity

Steps are listed as numbered checks but there is no validation checkpoint or feedback loop reconciling results before producing the ranked output; the PASS/WARN/FAIL recording is implicit rather than an enforced verify step.

2 / 3

Progressive Disclosure

Well-organized single-file overview with clear sections (When to use, What to check, Output format, Examples) and no bundle files to navigate; appropriate for a self-contained inspection skill under the simple-skill carve-out.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concrete, trigger-rich, and cleanly answers both what and when, with a clear cost-optimization niche and natural user phrasings. It is an exemplar of the 'good_overall_examples' pattern.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Scans a project for the common Claude Code cost leaks and returns a prioritized fix list' — naming a concrete scan operation and a concrete output artifact.

3 / 3

Completeness

Explicitly answers both what ('Scans a project... returns a prioritized fix list') and when ('Trigger when the user asks to audit Claude Code costs...'), with an explicit 'Trigger when' clause.

3 / 3

Trigger Term Quality

Good coverage of natural user phrasings: 'my Claude bill is too high', 'optimize my CLAUDE.md', 'why is this project burning tokens', plus the explicit slash-command trigger '/cost-optimizer'.

3 / 3

Distinctiveness Conflict Risk

Clear niche — Claude Code cost auditing — with distinct cost/efficiency triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mergisi/awesome-openclaw-agents
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.