CtrlK
BlogDocsLog inGet started
Tessl Logo

context-degradation

This skill should be used for diagnosing and mitigating context degradation: lost-in-middle failures, context poisoning, context clash, context confusion, attention-pattern issues, and agent performance degradation caused by accumulated or conflicting context.

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

Advisory

Suggest reviewing before use

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 skill body with clear navigation to a real reference file and concrete mitigation guidance. The chief weakness is moderate verbosity from repeating concepts across sections.

Suggestions

Consolidate the 'Core Concepts' and 'Detailed Topics' sections to remove restated definitions of each degradation pattern, keeping the body lean.

Trim the attention-mechanic exposition (e.g., BOS attention-sink explanation) to the minimum needed to justify placement guidance, since Claude already understands attention basics.

DimensionReasoningScore

Conciseness

The body is mostly substantive domain knowledge rather than generic concepts Claude already knows, but patterns are restated across 'Core Concepts' and 'Detailed Topics' and some attention-mechanic exposition could be tightened, fitting the 'mostly efficient but could be tightened' anchor.

2 / 3

Actionability

Provides concrete thresholds (4K, 70%, 8K-16K tokens), a named four-bucket mitigation framework with use-conditions, worked examples, and a real reference script (degradation_detector.py), matching the 'specific examples, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sequenced detection-to-recovery flows (e.g., poisoning circuit-breaker steps 1-4) and a pattern-keyed mitigation framework give clear sequencing; the diagnostic nature does not require destructive-operation validation checkpoints.

3 / 3

Progressive Disclosure

SKILL.md is a well-organized overview with a single one-level-deep reference (patterns.md) and a script (degradation_detector.py), both clearly signaled with 'Read when' navigation guidance, matching the 'clear overview with well-signaled one-level references' anchor.

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, specific description with explicit activation triggers and a distinct niche. The main weakness is jargon-heavy trigger terms that some users would not naturally voice.

Suggestions

Add plain-language phrasing alongside technical terms (e.g., 'when the agent forgets earlier instructions or gets confused by long context') so users describe the problem in their own words.

Consider including a short 'Use when...' sentence restating the most common user-level symptom to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('diagnosing and mitigating') and specific failure modes (lost-in-middle, poisoning, clash, confusion, attention-pattern issues), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what ('diagnosing and mitigating context degradation') and when via the 'This skill should be used for...' trigger clause, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes some natural user phrases like 'agent performance degradation' and 'lost-in-middle failures,' but several terms ('context clash,' 'attention-pattern issues') are technical jargon a user would not naturally say, missing common variations.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (specific named degradation patterns) with distinct triggers unlikely to fire for adjacent skills, matching the 'clear niche with distinct triggers' anchor.

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.