cost-aware-llm-pipeline

Cost optimization patterns for LLM API usage — model routing by task complexity, budget tracking, retry logic, and prompt caching. Use when LLM spend needs to come down, or when routing tasks across model tiers and budgets.

Quality

83%

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

Quality

Content

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

A well-structured, code-first skill with executable core patterns and a clear composition workflow. The main weakness is the Composition example's reliance on undefined helper functions and placeholders that prevent it from being fully copy-paste ready.

Suggestions

Define or stub the helpers used in the Composition example (build_cached_messages, parse_result, Config, BudgetExceededError) so the pipeline snippet is fully runnable.

Fill the `...` placeholders in CostRecord construction (input_tokens, output_tokens, cost_usd) with concrete extraction from the API response.

Add an explicit feedback loop for budget exhaustion (e.g., what to do when over_budget besides raising) to strengthen the workflow's validation checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is code-first and lean, assuming Claude's competence without explaining basic LLM or programming concepts; only minor instances (some Best Practices lines restate what the code already shows) could be trimmed, keeping it just below the 5-anchor.	4 / 5
Actionability	The four core snippets (select_model, CostTracker, call_with_retry, caching) are concrete and executable, but the Composition example relies on undefined helpers (build_cached_messages, parse_result, Config) and `...` placeholders, leaving minor gaps short of copy-paste-ready.	4 / 5
Workflow Clarity	The Composition section sequences four numbered steps (route, check budget, call with retry+caching, track cost) with a budget-check checkpoint, but lacks an explicit validate→fix→retry feedback loop for the overall process, capping it below 5.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with clear section headers (Core Concepts, Composition, Pricing Reference, Best Practices, Anti-Patterns); at ~180 lines it is well-organized but slightly longer than the simple-skill case that would earn a 5.	4 / 5
	Total	16 / 20 Passed

Description

92%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, specific description that clearly states both what the skill does and when to use it, with concrete technique names and natural trigger phrases. The only minor gap is keyword synonym coverage for cost-reduction phrasing.

Dimension	Reasoning	Score
Specificity	"model routing by task complexity, budget tracking, retry logic, and prompt caching" lists four concrete, distinct techniques — comprehensive coverage of the domain's actions, matching the top anchor rather than the 4-anchor (only minor gaps).	5 / 5
Completeness	It explicitly states what ("Cost optimization patterns for LLM API usage — model routing...") and when ("Use when LLM spend needs to come down, or when routing tasks across model tiers and budgets"), with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	"LLM spend needs to come down" and "routing tasks across model tiers and budgets" are natural phrases a user would say, but common variants like "reduce API costs" or "save on LLM bills" are missing, so it sits above the 3-anchor but below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The LLM-API cost-optimization niche with triggers like "LLM spend" and "model tiers and budgets" is clearly distinct from general coding or generic API skills, with minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/cost-aware-llm-pipeline/SKILL.md
Commit: 06c5e11

Reviewed: 3 days 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.