CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

context-window-management

Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long context.

Quality

66%

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 ./cli-tool/components/skills/ai-research/context-window-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

33%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 is a thin skeleton: headers exist but nearly every section lacks substance — patterns are one-line abstractions, anti-patterns are empty headings, the persona preamble is cut off mid-sentence, and no concrete technique, threshold, or code example is ever given. It reads as an unfinished draft rather than usable guidance for managing context windows.

Suggestions

Replace the persona preamble and the redundant 'Capabilities' noun list with concrete decision rules, e.g. token-count thresholds that determine when to summarize vs. trim vs. route ('Tiered Context Strategy' currently never states its tiers).

Flesh out each Pattern with executable guidance (specific ordering techniques, summarization-by-importance criteria, trimming rules) and give every Anti-Pattern heading a concrete countermeasure — currently all three are empty.

Fix the truncated text at 'Your cor' and remove it entirely along with the filler persona; the broken sentence signals the file was cut off before completion.

DimensionReasoningScore

Conciseness

The body is short and mostly terse, but the persona preamble ('You're a context engineering specialist who has optimized LLM applications handling millions of conversations...') and the 'Capabilities' list (which restates the description as bare nouns) are unnecessary padding, matching anchor 3's 'some unnecessary explanation or could be tightened'.

3 / 5

Actionability

No code, commands, or concrete parameters anywhere; the patterns are single-line hints ('Different strategies based on context size', 'Place important content at start and end') and the Anti-Patterns are empty headings — anchor 2's 'high-level hints but missing the specific steps to execute', and not anchor 1 only because those one-liners are real directives.

2 / 5

Workflow Clarity

No sequence or steps exist: 'Tiered Context Strategy' promises 'Different strategies based on context size' but never enumerates the tiers or their thresholds, and there is no decision order for when to summarize vs. trim vs. route and no checkpoints — matching anchor 1 ('steps missing or incoherent').

1 / 5

Progressive Disclosure

Under 50 lines with no external file references needed and clearly headed sections, but the truncated persona text ('Your cor') and three completely empty Anti-Pattern sections are real organization gaps, holding it below anchor 5's 'well-organized sections' bar for simple skills.

4 / 5

Total

10

/

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.

The description is strong: it explicitly states what the skill covers and includes a clear 'Use when:' clause with natural trigger terms. Main weaknesses are the nominal 'Strategies for...' framing instead of direct action verbs and a missing sentence break before 'Use when:', plus a few absent trigger synonyms.

DimensionReasoningScore

Specificity

Names the domain ('managing LLM context windows') and lists several concrete operations ('summarization, trimming, routing, and avoiding context rot'), though framed nominally ('Strategies for...') rather than as direct third-person verbs, keeping it below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers 'what' (strategies for managing context windows via summarization, trimming, routing) and 'when' via a literal 'Use when:' clause listing five concrete trigger phrases, matching the anchor-5 pattern of both halves explicitly stated.

5 / 5

Trigger Term Quality

'context window, token limit, context management, context engineering, long context' are natural phrases users would say, with good coverage; a few common variations (e.g. 'context length', 'trim conversation') are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (LLM context window management) with distinct triggers, but terms like 'context management'/'context engineering' overlap with closely related skills it itself cites (conversation-memory, prompt-caching), so minor overlap risk keeps it at anchor 4 rather than 5.

4 / 5

Total

17

/

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_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

davila7/claude-code-templates

Path

cli-tool/components/skills/ai-research/context-window-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.