token-budget-advisor

Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

85%

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

A well-structured, highly actionable skill body with a clear sequenced workflow and concrete formulas/templates. The main weakness is redundancy: trigger terms and the precision disclaimer are repeated across multiple sections and could be consolidated to save tokens.

Suggestions

Consolidate trigger-term examples: the "Examples → Triggers/Does Not Trigger" section largely duplicates the "When to Use" list and the description's TRIGGER/DO NOT TRIGGER clauses — keep one canonical set and reference it, or trim the Examples section to only novel cases.

Remove the duplicated precision disclaimer: the "~85-90% accuracy (±15%)" line appears both inside the Step 3 code block and again in the standalone "Precision note" section — keep it in one place.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (lean tables, formulas, no basic-concept padding), but trigger examples are duplicated across the description, "When to Use", and "Examples" sections, and the ~85-90% accuracy disclaimer appears both in the Step 3 block and the "Precision note" — content that could be tightened.	2 / 3
Actionability	It gives concrete executable guidance: token formulas (`words × 1.3`, `chars / 4`), a complexity multiplier table, level-token estimate formulas, a copy-paste prompt template, and a level/length table — copy-paste ready and specific.	3 / 3
Workflow Clarity	A clear four-step sequence (estimate input → estimate response → present options → respond) with the Shortcuts section handling edge cases and silent session-level maintenance; the operation is non-destructive, so the absence of validation checkpoints does not cap the score.	3 / 3
Progressive Disclosure	No bundle files exist, so the skill is appropriately self-contained; content is well-organized into clearly headed sections with one clearly-signaled cross-skill reference ([context-budget](../context-budget/SKILL.md)), matching the 'well-organized sections' expectation.	3 / 3
	Total	11 / 12 Passed

Description

90%

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, third-person description that clearly states its purpose, provides rich natural trigger terms (including Spanish), and explicitly separates positive from negative triggers. Its only weakness is that it names a single concrete action rather than enumerating multiple specific capabilities.

Dimension	Reasoning	Score
Specificity	The description states one concrete action ("Offers the user an informed choice about how much response depth to consume before answering") but does not list multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the 'multiple specific concrete actions' level above.	2 / 3
Completeness	It explicitly answers what ("Offers the user an informed choice...") and when ("Use this skill when...", "TRIGGER when:", "DO NOT TRIGGER when:"), matching the 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	It provides broad coverage of natural phrases users would say ("token budget", "short version", "brief answer", "detailed answer", "exhaustive answer") plus Spanish variants, matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (response-depth control) and the DO NOT TRIGGER clause explicitly disambiguates auth/session/payment tokens, making conflict with other skills unlikely.	3 / 3
	Total	11 / 12 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
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

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.