cost-aware-llm-pipeline

Cost optimization patterns for LLM API usage — model routing by task complexity, budget tracking, retry logic, and prompt caching.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

A well-organized, mostly concrete skill body with executable examples and a clear pipeline sequence, weakened by a stale-prone pricing table, an incomplete Composition example, and missing batch-level validation feedback loops.

Suggestions

Move the time-sensitive pricing table into a reference file or a clearly version-labeled section, and merge the redundant 'When to Use' into 'When to Activate'.

Make the Composition example fully executable — define Config/BudgetExceededError/build_cached_messages, add 'import time', and replace '...' placeholders — or explicitly label it as illustrative pseudocode.

Add per-item budget validation and a batch error-recovery feedback loop to the pipeline workflow, since batch processing is a primary use case.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and code-heavy, but the 'Pricing Reference (2025-2026)' table embeds time-sensitive version numbers and dates outside a deprecated/old-patterns section, and 'When to Use' largely restates 'When to Activate'.	2 / 3
Actionability	Most code blocks (select_model, CostTracker) are executable, but the Composition example uses '...' placeholders and undefined symbols (Config, BudgetExceededError, build_cached_messages) and call_with_retry references time.sleep without importing time.	2 / 3
Workflow Clarity	The Composition section gives a clear 4-step sequence with a budget checkpoint, but batch processing — a stated core use case — lacks per-item budget validation and an error-recovery feedback loop, which caps the score at 2.	2 / 3
Progressive Disclosure	The skill is a single self-contained file with well-organized sections (When to Activate, Core Concepts, Composition, Best Practices, Anti-Patterns) and no nested references, giving easy navigation.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 specific and distinctive description that names four concrete techniques, but it omits an explicit 'when to use' trigger clause and leans on technical jargon over natural user phrasing.

Suggestions

Add a 'Use when...' clause with natural triggers, e.g. 'Use when building apps that call LLM APIs, processing batches of items, or needing to stay within an API spend budget.'

Include user-facing phrasing alongside jargon, such as 'reduce LLM API costs', 'API budget limits', and 'cheaper model routing'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete patterns — 'model routing by task complexity, budget tracking, retry logic, and prompt caching' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' (cost optimization patterns with four named techniques) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Terms like 'LLM API usage' and 'cost optimization' are relevant, but 'model routing by task complexity' and 'prompt caching' are technical jargon rather than phrases a user would naturally say, and common variations are missing.	2 / 3
Distinctiveness Conflict Risk	'Cost optimization patterns for LLM API usage' carves out a clear niche with specific techniques, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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/everything-claude-code
Commit: 4130457

Reviewed: 4 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.