CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

context-budget

Audits Claude Code context window consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/context-budget/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 audit workflow with specific thresholds, formulas, and a concrete output template that scores consistently at 4 across all dimensions. The main improvement opportunities are de-duplicating facts repeated between phases and Best Practices, and adding executable scan commands.

Suggestions

De-duplicate Best Practices: "~500 tokens per tool" and "agent descriptions are loaded always" are already stated in Phases 1 and 3 — keep each fact in one place.

Add a few copy-paste inventory commands (e.g., find/wc one-liners for counting lines and tokens per component file) to make the audit directly executable.

Consider moving the 28-line report template and Examples into a references/ file, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

Efficient instruction-only content that assumes Claude's competence (no explanations of what MCP or tokens are) and delivers specific thresholds and formulas. Minor duplication — "~500 tokens per tool" and "agent descriptions are loaded always" each appear in both the phases and Best Practices — keeps it below anchor 5's "every token earns its place".

4 / 5

Actionability

Concrete guidance throughout: exact scan paths (agents/*.md, skills/*/SKILL.md, .mcp.json), exact thresholds (>200 lines, >30 words, >20 tools), estimation formulas (words × 1.3, chars / 4), and a full report template. Falls short of anchor 5 only because no copy-paste executable commands (e.g., shell one-liners for the inventory scan) are provided.

4 / 5

Workflow Clarity

A clear four-phase sequence (Inventory → Classify → Detect Issues → Report) with well-defined sub-steps per phase. The workflow is read-only analysis, so the destructive/batch validation cap does not apply, but minor validation gaps (e.g., verifying estimates, handling absent component types) keep it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Self-contained single-file skill with no bundle files (references/, scripts/, assets/ all absent) and well-organized, clearly headed sections. At ~128 lines it exceeds the under-50-line simple-skill exception for a 5, and the 28-line report template plus Examples could arguably be split into a reference file, matching anchor 4's "minor organization gaps".

4 / 5

Total

16

/

20

Passed

Description

66%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 specific, third-person description with good domain keywords and a clear niche, but it omits any "when to use" trigger guidance, which caps completeness and limits trigger-term quality. Adding an explicit "Use when..." clause would lift it into the top tier.

Suggestions

Append a trigger clause such as: "Use when the session feels sluggish, after adding agents/skills/MCP servers, when you want to know remaining context headroom, or when running /context-budget."

Include natural user phrasings like "context bloat", "running out of context", or "context headroom" to broaden trigger-term coverage.

State the concrete output artifact (e.g., "produces a prioritized context budget report") instead of the vaguer "recommendations".

DimensionReasoningScore

Specificity

Lists three concrete actions — "Audits... context window consumption", "Identifies bloat, redundant components", "produces prioritized token-savings recommendations" — across a named domain (agents, skills, MCP servers, rules). More specific than anchor 3's 1-2 actions, but "produces recommendations" is less concrete than anchor 5's comprehensive action list.

4 / 5

Completeness

The "what" is clear (audit consumption, identify bloat, produce recommendations), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. A score of 4 requires both "what" and "when" to be present.

3 / 5

Trigger Term Quality

Contains natural terms users would say — "context window", "bloat", "token-savings", "MCP servers" — with better coverage than anchor 3's bare domain naming. Falls short of anchor 5 because common variations like "context is full", "running out of context", or "context bloat" are missing.

4 / 5

Distinctiveness Conflict Risk

"Claude Code context window consumption" carves a clear niche with only minor overlap risk against generic optimization skills, matching anchor 4. Not 5 because anchor 5 pairs the niche with explicit distinct trigger phrases, which this description lacks.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/context-budget/SKILL.md

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.