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

78%

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 ./skills/cost-aware-llm-pipeline/SKILL.md

Quality

Content

67%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 pattern skill with mostly executable code and a clear composition workflow. Its main weaknesses are redundant trigger sections, a stale-prone inline pricing table, and an incomplete composition example with no budget-exceeded recovery loop.

Suggestions

Merge the duplicated "When to Activate" and "When to Use" sections into a single trigger list to remove ~10 lines of redundancy.

Move the 2026 pricing table to a references file (e.g. references/pricing.md) so time-sensitive numbers can be updated without editing the skill body.

Make the Composition example executable — define or import Config, build_cached_messages, parse_result, and BudgetExceededError, import time in the retry snippet, and add guidance on what to do when BudgetExceededError is raised (e.g. halt batch, report spend, optionally re-route to a cheaper model).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with lean code examples, but the "When to Activate" and "When to Use" sections duplicate nearly identical trigger lists, and the dated "Pricing Reference (2026)" table is time-sensitive content not placed in a deprecated/old-patterns section — more than the minor trimming implied by the score-4 anchor.	3 / 5
Actionability	select_model, CostTracker, and call_with_retry are concrete and executable, but the Composition example references undefined names (Config, build_cached_messages, parse_result, estimated_items, BudgetExceededError, client) and uses time.sleep without importing time — minor gaps keeping it below fully copy-paste ready.	4 / 5
Workflow Clarity	The Composition section clearly sequences route → budget check → retry+caching call → immutable tracking, with the budget check acting as an explicit checkpoint; however, there is no guidance on recovering after BudgetExceededError and no per-item budget re-check for batch loops, so it falls short of the explicit-feedback-loops anchor.	4 / 5
Progressive Disclosure	The single ~190-line file is well organized into clearly signaled sections with no nested references, but the dated pricing table is content that belongs in a separate reference file so it can be updated independently, and the skill does not qualify for the under-50-lines simple-skill exemption.	4 / 5
	Total	15 / 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: third-person, concrete about both capabilities and activation triggers, with natural phrasing a user would plausibly say. The only weakness is incomplete synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	The description lists four concrete, specific capabilities — "model routing by task complexity, budget tracking, retry logic, and prompt caching" — comprehensively covering the skill's own techniques, matching the multiple-specific-actions anchor rather than the minor-gaps anchor.	5 / 5
Completeness	It explicitly answers both what ("Cost optimization patterns ... model routing, budget tracking, retry logic, and prompt caching") 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 both-what-and-when anchor.	5 / 5
Trigger Term Quality	Good natural phrases such as "LLM spend needs to come down", "routing tasks across model tiers", and "Cost optimization" for LLM API usage, but common variations users would say (e.g. "reduce API costs", "cheaper model", "token costs") are missing, so it falls short of the comprehensive-synonym anchor.	4 / 5
Distinctiveness Conflict Risk	The niche (LLM API cost optimization) is mostly distinct with triggers tied to spend and model tiers, but there is minor overlap risk with generic optimization or pipeline-orchestration skills, fitting the mostly-distinct anchor rather than the minimal-conflict one.	4 / 5
	Total	18 / 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: c70874f

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.