CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-context-management

Comprehensive context management strategies for cost optimization and infinite-length conversations. Covers server-side clearing (tool results, thinking blocks), client-side SDK compaction (automatic summarization), and memory tool integration. Use when managing long conversations, optimizing token costs, preventing context overflow, or enabling continuous agentic workflows.

67

Quality

80%

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/claude-context-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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, actionable skill body with sequenced workflow and correctly signaled, real reference files. It is held back by verbosity (redundant sections, basic-concept definitions, time-sensitive metadata) that competes with the context budget.

Suggestions

Remove or trim the 'Key Concepts' section — definitions like 'Context Window' and 'Input Tokens' are knowledge Claude already has and add tokens without value.

Drop the hard-coded 'Last Updated: November 2025' and the enumerated 'Supported Models' list, or move them into a reference file, since version/date details drift and penalize conciseness.

Collapse 'Strategies Overview' into the existing 'Workflow' / 'Feature Comparison' content to avoid restating the same server-side vs client-side distinction three times.

DimensionReasoningScore

Conciseness

The body is mostly useful but pads with a 'Key Concepts' section defining terms Claude already knows (Context Window, Input Tokens), restates material in 'Strategies Overview', and embeds time-sensitive 'Last Updated: November 2025' and a model-version list that will drift.

3 / 5

Actionability

Three concrete, largely copy-paste-ready Python examples with real parameters (clear_tool_uses_20250919, exclude_tools, compaction_control), with only a minor gap where the memory example leaves messages=[...].

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced and Step 6 supplies a validation checklist plus an adjustment feedback loop; validation is concentrated in the final step rather than inline at each fragile step.

4 / 5

Progressive Disclosure

Clear section structure and a 'Next Steps' block pointing to four one-level-deep reference files that all exist on disk; the body is somewhat large, with material (Feature Comparison, Strategies Overview) that could live in the references.

4 / 5

Total

15

/

20

Passed

Description

92%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, specific description that states concrete capabilities and an explicit trigger clause in third-person voice. Minor synonym coverage gaps in trigger terms keep it just below a perfect trigger-term score.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'server-side clearing (tool results, thinking blocks), client-side SDK compaction (automatic summarization), and memory tool integration' — giving comprehensive coverage of specific actions.

5 / 5

Completeness

Explicitly answers both what (three named strategies) and when (a concrete 'Use when…' trigger clause), matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when managing long conversations, optimizing token costs, preventing context overflow, or enabling continuous agentic workflows' clause offers good natural-term coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (context management for Claude conversations) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.