CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

83%

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

The canonical home for this skill is claude-context-management in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 body delivers an actionable, well-sequenced workflow with executable code and a clean reference structure that matches the actual bundle. Its main weakness is token efficiency: key-concept definitions, narrative framing, a redundant strategies section, and self-assessment metadata add length without adding information Claude lacks.

Suggestions

Delete the 'Key Concepts' section and 'The Problem/Solution' framing in the Overview — Claude already knows what a context window or input tokens are; keep only skill-specific definitions like the clearing/compaction distinction if needed.

Remove the footer metadata ('Last Updated', 'Quality Score', 'Citation Coverage') and the 'Strategies Overview' section, which duplicates the decision framework and Quick Start content, trimming roughly 60 lines.

Consolidate Step 3's full parameter detail (trigger values, keep, exclude_tools) into references/server-side-context-editing.md and keep only the decision-level guidance inline, shortening SKILL.md toward a true overview.

DimensionReasoningScore

Conciseness

The core workflow, decision tables, and code examples are dense and useful, but there is real padding: the 'Key Concepts' section defines things Claude already knows ('Context Window: Maximum tokens available for input + output'), 'The Problem' narrates common knowledge, and the footer metadata ('Quality Score: 95/100', 'Citation Coverage') plus a redundant 'Strategies Overview' repeat content from Quick Start and Step 3. Not a 2 because the majority of the body is genuinely non-redundant guidance.

3 / 5

Actionability

Two of three Quick Start examples are fully executable with concrete parameters ('trigger': {'type': 'input_tokens', 'value': 100000}, betas list, exclude_tools), and the decision framework gives specific threshold ranges. Not a 5 because the memory example uses a 'messages=[...]' placeholder and '# Your other tools' comment instead of complete copy-paste code.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced, and Step 6 provides an explicit validation checklist plus a feedback loop ('Monitor first conversation end-to-end... Adjust trigger thresholds/exclusions... Repeat until optimal balance achieved'), with Step 5 adding monitoring metrics and remediation adjustments. This matches the top anchor's validate-and-retry pattern.

5 / 5

Progressive Disclosure

All four referenced files exist in the bundle, are one level deep, and each is announced with a bulleted summary of its contents ('See references/server-side-context-editing.md - All 6 parameters explained...'). Not a 5 because the ~400-line body still inlines content that could live in the references, such as the full parameter-level detail in Step 3, the Feature Comparison table, and the Strategies Overview section.

4 / 5

Total

16

/

20

Passed

Description

83%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 with a clear third-person statement of capabilities and an explicit 'Use when...' clause containing concrete trigger phrases. Its only weaknesses are a buzzword opener ('Comprehensive') and slightly incomplete natural-synonym coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities: 'server-side clearing (tool results, thinking blocks), client-side SDK compaction (automatic summarization), and memory tool integration'. Falls short of a 5 because 'Comprehensive context management strategies' is a buzzword-style opener and coverage omits configuration/monitoring actions the skill actually covers.

4 / 5

Completeness

Explicitly answers both: what ('server-side clearing... client-side SDK compaction... memory tool integration') and when ('Use when managing long conversations, optimizing token costs, preventing context overflow, or enabling continuous agentic workflows'). The when-clause contains concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

'managing long conversations, optimizing token costs, preventing context overflow, or enabling continuous agentic workflows' gives good natural-phrase coverage. A few natural synonyms users might say are missing, such as 'context window limits', 'compact/summarize the conversation', or 'reduce token usage', keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

The clearing/compaction/memory-tool niche is distinct, but 'optimizing token costs' overlaps with generic cost-optimization skills and the phrase is broad enough that a cost-focused query could route to the wrong skill. Mostly distinct with minor overlap risk.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/claude-context-management/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.