CtrlK
BlogDocsLog inGet started
Tessl Logo

context-optimization

This skill should be used for improving context efficiency: context budgeting, observation masking, prefix or KV-cache strategy, partitioning, token-cost reduction, retrieval scoping, and extending effective context capacity without lowering answer quality.

60

Quality

70%

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-optimization/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.

The body is well-structured, actionable, and workflow-oriented with strong feedback loops and a properly signaled reference file. Its main weakness is conciseness — section-to-section redundancy and some over-explanation of basics inflate the token budget.

Suggestions

Collapse the overlap between Core Concepts and Detailed Topics so each technique is described once; defer deeper detail to optimization_techniques.md.

Trim basic explanations Claude already knows (e.g. what KV-cache tensors are) to lift conciseness.

Link the existing compaction.py script from the body (e.g. in the Compaction or Examples section) so the bundle file is discoverable rather than orphaned.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete thresholds and tight prose, but Core Concepts and Detailed Topics overlap (compaction, masking, KV-cache each described twice) and some basic explanations (e.g. what KV-cache stores) pad the text.

3 / 5

Actionability

Provides executable code examples, concrete thresholds (70%, 80%), an explicit prompt ordering, and a copy-pasteable reference format, with only minor gaps in example completeness.

4 / 5

Workflow Clarity

A clear priority-ordered strategy sequence and decision-framework table are present, plus a measure-optimize-remeasure feedback loop ('If an optimization technique does not measurably improve the target metric, remove it'); minor validation-checkpoint gaps remain.

4 / 5

Progressive Disclosure

Good section structure with a clearly signaled one-level reference ('Read when:' guidance to optimization_techniques.md); minor gaps are the dense inline Detailed Topics and the unreferenced compaction.py script.

4 / 5

Total

15

/

20

Passed

Description

72%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 specific and comprehensive about capabilities with a clear use-condition, but its trigger terms skew technical and would benefit from more natural user-facing phrasing. Distinctiveness is strong given the tactic-level focus.

Suggestions

Add natural-language trigger phrases users would actually say (e.g. 'Use when the user mentions context window limits, token costs, or running out of context').

Soften jargon like 'observation masking' and 'KV-cache strategy' with plain-language synonyms to improve trigger term quality.

Make the 'when' clause more concrete by listing explicit situational triggers rather than a single general condition.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'context budgeting, observation masking, prefix or KV-cache strategy, partitioning, token-cost reduction, retrieval scoping' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly states both what (the enumerated optimization tactics) and when ('This skill should be used for improving context efficiency'), but the when is a single general condition rather than concrete user-facing trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are present but lean technical ('observation masking', 'prefix or KV-cache strategy') rather than natural user phrasing; common synonyms like 'context window' or 'token usage' are missing.

3 / 5

Distinctiveness Conflict Risk

The niche is clear and tactic-specific, making overlap unlikely with unrelated skills; minor residual overlap risk with closely related context skills (compression, fundamentals).

4 / 5

Total

16

/

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
muratcankoylan/Agent-Skills-for-Context-Engineering
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.