CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-cost-optimization

Comprehensive cost tracking and optimization for production Claude deployments. Covers Admin API usage tracking, efficiency measurement, ROI calculation, optimization patterns (caching, batching, model selection, context editing, effort parameter), and cost prediction. Use when tracking costs, optimizing token usage, measuring efficiency, calculating ROI, reducing production expenses, or implementing cost-effective Claude integrations.

Quality

81%

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

63%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 actionable and well-sequenced, with executable code, concrete savings figures, and a clear 5-step workflow plus decision tree. Its main weaknesses are token redundancy — a near-duplicate Quick Start code block, ROI and pricing stated multiple times, and overview sections restating the description — and weak progressive disclosure, with 3 of 4 reference files never named and bundle content duplicated inline.

Suggestions

Remove the duplicated 'Quick Start' sections (their code and ROI examples restate Steps 1 and 5 almost verbatim), or collapse each into a one-line pointer to the corresponding workflow step.

Consolidate pricing into a single location (e.g., references/cost-analysis.md, which already contains it) and link to it, eliminating the triplicated pricing data and the inline 'as of November 2025' date-stamped table.

Replace the vague 'see references/ directory' closer with explicit named links and one-line descriptions for cost-analysis.md, efficiency-measurement.md, and optimization-strategies.md.

DimensionReasoningScore

Conciseness

Core material is skill-specific and dense (pricing tables, savings percentages, decision tree, scenarios), but there is real redundancy: the ~40-line Step 1 usage snippet is nearly duplicated in "Quick Start - Usage Tracking" (`get_monthly_costs()`), ROI appears twice (Step 5 prose plus a Quick Start function), pricing is stated three times (Step 3, the Quick Start code comment, and the date-stamped "Pricing Overview (as of November 2025)" table), and "Why This Matters"/"Key Savings"/"When to Use This Skill" largely restate the description. Not 2: it never explains concepts Claude already knows; not 4: the duplicated code block and triple-stated pricing exceed 'minor instances of over-explanation'.

3 / 5

Actionability

Provides fully executable, copy-paste-ready Python (`get_monthly_costs()`, `calculate_roi()`), concrete optimization directives with expected savings ("Effort Parameter... low effort (50-70% savings)"), and a decision tree covering common cases. Not 5: minor gaps in the flagship example — `thirty_days_ago` is computed but never used, no date filter is actually passed despite the 'last 30 days' comment, and `cost_before_claude: float = None` is not Optional-typed; not 3: the code is real and executable, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

The "5-Step Optimization Workflow" (Measure Baseline → Analyze Cost Drivers → Apply Optimizations → Track Improvements → Report ROI) is clearly sequenced, and Step 4 ("Quality impact (did results improve or worsen?)", "Track for 1-2 weeks per optimization") functions as a checkpoint, reinforced by the decision tree. Not 5: validation is implicit — no explicit verify/rollback criteria if quality degrades after an optimization; not 3: sequence and checkpoints are mostly present, not absent.

4 / 5

Progressive Disclosure

One reference is clearly signaled ("See references/usage-tracking.md for detailed Admin API integration"), but the closing pointer "see references/ directory" never names the other three bundle files (cost-analysis.md, efficiency-measurement.md, optimization-strategies.md), and detail content that exists in the bundle (the pricing table duplicating cost-analysis.md) is inlined in the body. Not 4: most of the bundle's reference files are not individually signaled and separate-file content is duplicated inline; not 2: the body is well-sectioned and references are one level deep with no nesting.

3 / 5

Total

14

/

20

Passed

Description

88%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.

A strong description: it explicitly states what the skill does with a comprehensive, concrete action list and follows with an explicit 'Use when...' trigger clause containing natural user phrases, all in third person. Weaknesses are minor — a few missing common synonyms (save money, cut costs, budget) and slight overlap risk with adjacent token-reduction skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions spanning the domain: "Admin API usage tracking, efficiency measurement, ROI calculation, optimization patterns (caching, batching, model selection, context editing, effort parameter), and cost prediction" — comparable in specificity to the anchor-5 example's full action list. Not 4: coverage is comprehensive across tracking, analysis, optimization, and reporting with no notable gaps.

5 / 5

Completeness

Clearly answers both: what ("Comprehensive cost tracking and optimization for production Claude deployments. Covers Admin API usage tracking...") and when (explicit "Use when tracking costs, optimizing token usage..." with concrete trigger phrases). Matches the anchor-5 example structure exactly; the adjacent anchors lack either explicit triggers or a clear 'what'.

5 / 5

Trigger Term Quality

The trigger clause "Use when tracking costs, optimizing token usage, measuring efficiency, calculating ROI, reducing production expenses, or implementing cost-effective Claude integrations" contains multiple natural phrases users would say. Not 5: common synonyms like "save money", "cut costs", "token costs", or "budget" are missing; not 3: keyword coverage is good and goes well beyond a single generic term.

4 / 5

Distinctiveness Conflict Risk

The production-cost/ROI niche is distinct and triggers are specific to cost concerns, but "optimizing token usage" overlaps with adjacent skills like context-management or tool-optimization skills that also reduce tokens. Not 5: minor overlap risk with closely related optimization skills; not 3: the cost/ROI framing is much more specific than generic "works with document files"-level descriptions.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/Skrillz

Path

skills/claude-cost-optimization/SKILL.md

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.