Name: autonomous-cost-optimizer
Rating: 58.4 (1 reviews)
Author: fernandezbaptiste

autonomous-cost-optimizer

Token and cost optimization for autonomous coding. Use when tracking token usage, optimizing API costs, managing budgets, or improving efficiency.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/autonomous-cost-optimizer/SKILL.md

The canonical home for this skill is autonomous-cost-optimizer in fernandezbaptiste/Skrillz

Quality

Content

57%Weight 40%Scale 1-5

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

The body is well-structured with executable quick-start code and a clear workflow diagram, but it ships broken references (missing references/ directory and two missing scripts) and lacks validation checkpoints for budget/batch operations. Code examples also contain execution gaps.

Suggestions

Create the missing `references/PRICING-GUIDE.md` and `references/OPTIMIZATION-STRATEGIES.md`, or remove the references and scripts entries for files that do not exist (`budget_manager.py`, `efficiency_analyzer.py`).

Add a validation checkpoint to the workflow, e.g. verify `is_within_budget()` before proceeding and a confirm-or-retry loop when `enter_efficiency_mode()` is triggered.

Fix the quick-start code: define `project_dir`, wrap the `await enter_efficiency_mode()` example in an `async` function, or drop `await` if the method is synchronous.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with lean tables and snippets, but the inline pricing table uses time-sensitive model versions/prices and the ASCII workflow diagram restates concepts Claude already knows, so it could be tightened.	3 / 5
Actionability	Quick-start provides concrete executable code with real method names, but `project_dir` is undefined, `await` appears outside an async context, and two referenced scripts do not exist.	4 / 5
Workflow Clarity	A TRACK->ANALYZE->OPTIMIZE->REPORT sequence is present, but budget enforcement and batch operations lack any validation or verification checkpoint, so workflow clarity is capped at 3 per the batch/destructive rule.	3 / 5
Progressive Disclosure	Sections are well organized and references are clearly signaled, but `references/` does not exist and two of four listed scripts are missing, so the signaled navigation leads to dead paths.	3 / 5
	Total	13 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 clearly answers both what the skill does and when to use it, with concrete trigger phrases and a distinct niche. Specificity is the weakest area: the stated actions are abstract nouns rather than concrete, mechanical operations.

Suggestions

Replace abstract action nouns with concrete operations, e.g. 'compacts context, caches repeated queries, batches similar operations, and enforces per-session budgets'.

Add common user-facing synonyms such as 'save money', 'reduce spending', 'cut costs', or 'spend limits' to broaden trigger coverage.

Tighten 'improving efficiency' to a more specific trigger (e.g. 'reducing token waste') to lower overlap risk with general performance skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ('tracking token usage, optimizing API costs, managing budgets, or improving efficiency') but they are abstract nouns rather than concrete mechanisms, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly states both the 'what' ('Token and cost optimization for autonomous coding') and a concrete 'when' clause with multiple trigger phrases, matching the anchor that requires both with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('tracking token usage', 'optimizing API costs', 'managing budgets'), but misses common synonyms like 'save money', 'reduce spending', 'cut costs', or 'spend'.	4 / 5
Distinctiveness Conflict Risk	The cost/token niche for autonomous coding is mostly distinct with clear triggers, but the broad 'improving efficiency' phrasing risks minor overlap with general performance skills.	4 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/autonomous-cost-optimizer/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.