CtrlK
BlogDocsLog inGet started
Tessl Logo

context-budget

Audita o peso de contexto carregado na sessão — CLAUDE.md, agents, MCP descriptions, rules ativas, skills invocadas e histórico acumulado. Estima tokens por componente, reporta headroom disponível e emite alertas de overflow. Distinto do cost-tracker (skill 30) que rastreia tokens gastos em completions runtime. Trigger em: "contexto inchado", "context overflow", "quanto contexto estou usando", "peso do contexto", "context budget", "tokens carregados", "sessao lenta", "respostas degradadas", "headroom de contexto", "custo fixo de contexto", "overhead de rules", "overhead dos agents", "impacto do MCP no contexto", "espaco no context window", "quanto cabe no context window"

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, highly actionable playbook: concrete commands, an explicit measure→act→re-measure checkpoint loop, and clean single-file organization. Its only weakness is mild padding — the description is re-stated in the body and the sample report template is longer than needed.

Suggestions

Trim the 'Distinção crítica' section to one line — the frontmatter description already states the distinction from skill 30, so the body only needs a pointer.

Compress the Fase 3 example report to a skeleton (header rows plus 1-2 filled rows) instead of a fully populated 12-row table with invented numbers.

Move the per-model threshold table (Fase 4) and the full report template into a references/ file, keeping SKILL.md as a compact overview.

DimensionReasoningScore

Conciseness

The body is dense and operational (commands, thresholds, heuristics) but has minor trimmable padding: the 'Distinção crítica' block repeats the frontmatter description and the Fase 3 worked example carries ~35 lines of invented sample numbers. Fits anchor 4 ('minor instances of over-explanation that could be trimmed') rather than 5, and the padding is incidental rather than the unnecessary concept explanations of anchor 3.

4 / 5

Actionability

Copy-paste-ready commands throughout ('find .claude/rules/ -name "*.md" | xargs wc -c', 'claude mcp remove <name>', '/clear'), a concrete token estimation heuristic (~4 chars/token with a stated 10-20% correction), per-model threshold tables, and a complete output template — matching the anchor-5 'fully executable, specific examples cover the common cases'.

5 / 5

Workflow Clarity

Fases 0–4 form a clear, ordered audit sequence, and the Checkpoint paragraph provides an explicit validation feedback loop ('aplicar a ação mais barata primeiro… → medir de novo (Fase 1) → se o sintoma persistir, aplicar a próxima ação'), including guidance not to skip to irreversible changes without confirming the cheap fix failed — matching anchor 5.

5 / 5

Progressive Disclosure

The ~155-line body is self-contained with clear section headers, no bundle files exist, and no referenced paths are broken. Anchor 4 fits ('good structure; most content appropriately placed; minor organization gaps'): the Fase 3 report template and the model-threshold table are inlined and could live in separate reference files at this length.

4 / 5

Total

18

/

20

Passed

Description

100%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 voice, concrete capabilities, a rich bilingual trigger list, and an explicit differentiation from the nearest neighboring skill. All four dimensions sit at the top anchor.

DimensionReasoningScore

Specificity

The description lists four concrete actions ('Audita o peso de contexto…', 'Estima tokens por componente', 'reporta headroom disponível', 'emite alertas de overflow') and enumerates the exact components audited (CLAUDE.md, agents, MCP descriptions, rules, skills, histórico), giving comprehensive coverage with no gaps — matching the anchor-5 example rather than the 'minor gaps' of anchor 4.

5 / 5

Completeness

It explicitly answers 'what' (audits, estimates, reports, alerts) and 'when' via the dedicated 'Trigger em:' clause with concrete trigger phrases, matching anchor 5. It is not capped at 3 because explicit trigger guidance is present rather than missing.

5 / 5

Trigger Term Quality

The 'Trigger em:' clause supplies 15 natural user phrases ('contexto inchado', 'context overflow', 'quanto contexto estou usando', 'sessao lenta', 'quanto cabe no context window') in both Portuguese and English with synonyms, which is comprehensive natural-term coverage as required by the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — tokens loaded into context before any completion — and explicitly draws the boundary against the adjacent skill: 'Distinto do cost-tracker (skill 30) que rastreia tokens gastos em completions runtime', so overlap/conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
felvieira/claude-skills-fv
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.