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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 reference with clear workflows and disciplined progressive disclosure. The main drag on token efficiency is conceptual explanation Claude does not need and some threshold repetition across sections.

Suggestions

Trim or remove the explanatory KV-cache primer ('KV-cache stores Key and Value tensors computed during inference...') and cache-stability prose, since Claude already knows this; keep only the actionable ordering rules.

Consolidate the repeated 70%/80% compaction thresholds into one authoritative location and cross-reference it instead of restating in Core Concepts, Detailed Topics, and Budget Management.

Mark the code examples that call illustrative stubs (e.g. compact_context, store_observation) as patterns rather than runnable functions, or replace them with the real implementations from scripts/compaction.py.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but it explains concepts Claude already knows ('KV-cache stores Key and Value tensors computed during inference...') and repeats threshold figures across the Core Concepts, Detailed Topics, and Performance Targets sections.

2 / 3

Actionability

It provides concrete code snippets, a decision-framework table mapping context composition to first/second actions, specific thresholds (70%, 80%, 50-70% reduction), and measurable performance targets.

3 / 3

Workflow Clarity

A clear priority ordering, trigger-based signals, and explicit validation checkpoints ('Validate that all partitions completed before merging', 're-validate the summary against the current task goal') plus measure-then-optimize-then-measure feedback loops structure the work.

3 / 3

Progressive Disclosure

The body points to a single real one-level-deep reference (./references/optimization_techniques.md) with explicit 'Read when' signals, and the References section cleanly separates internal, related-skill, and external resources.

3 / 3

Total

11

/

12

Passed

Description

85%

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 that pairs an explicit activation trigger with a concrete, multi-action capability list and a well-bounded niche. Its only real weakness is trigger terms that skew technical, missing some natural user phrasings.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'context budgeting, observation masking, prefix or KV-cache strategy, partitioning, token-cost reduction, retrieval scoping' — rather than vague language.

3 / 3

Completeness

'This skill should be used for improving context efficiency: ...' provides an explicit trigger (when) alongside a concrete capability list (what), satisfying both halves.

3 / 3

Trigger Term Quality

Keywords like 'context budgeting', 'observation masking', 'KV-cache', and 'retrieval scoping' are relevant but lean technical, and common user phrasings ('reduce tokens', 'fit more in context', 'cache the prefix') are only partially covered.

2 / 3

Distinctiveness Conflict Risk

It carves a clear context-efficiency niche with specific triggers, making it unlikely to fire for the adjacent context-compression or context-fundamentals skills.

3 / 3

Total

11

/

12

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.