CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is highly actionable with concrete formulas, tables, and a reusable presentation template, organized into a clear four-step workflow. Its main shortfalls are minor redundant restatements of the accuracy disclaimer and the absence of explicit validation feedback loops, which keep conciseness and workflow clarity just below the top anchors.

Suggestions

Consolidate the accuracy disclaimer into a single location (the Step 3 block) and remove the redundant 'Precision note' section, or vice versa, to tighten conciseness.

Add a brief explicit checkpoint after presenting the depth options (e.g., 'Wait for the user's selection before proceeding; if ambiguous, default to 50% Moderate and state the assumption') to push workflow clarity toward the top anchor.

Consider splitting the complexity multiplier table and shortcuts table into a reference file if the skill grows, to improve progressive disclosure scalability.

DimensionReasoningScore

Conciseness

The body is largely efficient — dense tables, formulas, and a copy-paste presentation block — with only minor trimmable redundancy: the ~85-90% accuracy disclaimer appears both in the Step 3 block and again in the 'Precision note' section, and the opening sentence restates the description. It is not verbose enough to drop to the 'noticeably verbose' anchor (3).

4 / 5

Actionability

Fully executable guidance: concrete token formulas ('words × 1.3', 'chars / 4'), a complexity→multiplier table, level token-estimate formulas, and a copy-paste presentation template with the actual estimated numbers slotted in, covering the common cases for an instruction-only skill.

5 / 5

Workflow Clarity

A clear four-step sequence (estimate input → estimate response → present options → respond at chosen level) with the user's depth selection acting as the interaction checkpoint, plus a 'Shortcuts' path and a silent-maintenance rule. It does not reach 5 because there are no explicit validation/error-recovery feedback loops, though none are strictly required for this non-destructive interaction flow.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with the one external reference (../context-budget/SKILL.md) and source link signaled at one level deep; the skill is intentionally self-contained (no references/scripts/assets bundle), so most content sits appropriately inline with only minor organization gaps rather than the ideal split of the top anchor.

4 / 5

Total

17

/

20

Passed

Description

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

The description is exemplary on trigger coverage, completeness, and distinctiveness, with explicit positive and negative trigger guidance and multilingual terms. Its only weakness is specificity, where a single core action is named rather than a comprehensive list of concrete capabilities.

Suggestions

Enumerate 2-3 concrete actions the skill performs (e.g., 'estimates input tokens, projects response size, and presents selectable depth levels') to lift specificity from a single action to several.

DimensionReasoningScore

Specificity

Names the domain (response-depth control) and one concrete action — 'Offers the user an informed choice about how much response depth to consume before answering' — but does not enumerate multiple distinct actions, so it stops at the 1-2 concrete actions anchor rather than the 'several specific actions' anchor (4).

3 / 5

Completeness

Explicitly answers 'what' (offers an informed choice about response depth before answering) and 'when' with concrete trigger phrases via 'Use this skill when...' / 'TRIGGER when:' / 'DO NOT TRIGGER when:', hitting the top anchor for both what and when.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms ('token budget', 'response length', 'short version', 'brief answer', 'detailed answer', 'exhaustive answer') plus Spanish variants ('cuántos tokens', 'ahorrar tokens', 'dame la versión corta'), matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (response-size/depth control) with explicit disambiguation that 'token' referring to auth/session/payment tokens should not trigger, minimizing conflict risk with unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.