context-degradation

Diagnose and mitigate LLM context window failure patterns in long agent conversations.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill context-degradation-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-degradation
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/context-degradation
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill context-degradation-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running agent conversations silently degrade: instructions get lost in the middle of the context, hallucinated content poisons later decisions, and contradictory facts produce inconsistent outputs. This Skill gives you a structured framework to identify which failure pattern is occurring and apply the right mitigation. ## Core Features & Use Cases - Five-Pattern Diagnosis: Classify failures as lost-in-middle, context poisoning, distraction, confusion, or clash, each with distinct symptoms and recovery steps. - Four-Bucket Mitigation: Apply Write (external scratchpads), Select (retrieval filtering), Compress (summarization), and Isolate (sub-agent separation) strategies to reduce context load. - Degradation Thresholds: Reference token-count thresholds per model to know when to trigger compaction before quality collapses. - Use Case: An agent that performed well early in a session starts contradicting earlier decisions and misusing tools. Use this Skill to trace the failure to context poisoning, cut the context back to a verified checkpoint, and restart with only validated information. ## Quick Start Ask the agent to diagnose why output quality dropped in this long conversation and recommend context mitigation steps.

Frequently Asked Questions about context-degradation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix lost-in-middle problems in long LLM contexts?▼

Place critical information at the start or end of the context, where attention is strongest. Use explicit section headers in long documents and surface key facts through summaries positioned in high-attention regions.

What is context poisoning in AI agents?▼

Context poisoning occurs when errors or hallucinations enter the context and get referenced by later decisions, amplifying the mistake. Recovery requires cutting the context back to before the contamination point and restarting with only verified information.

When does LLM performance degrade with long context?▼

Degradation thresholds vary by model: Claude Opus 4.5 begins degrading around 100K tokens, Sonnet 4.5 around 80K, and GPT-5.2 around 64K. Severe degradation occurs at roughly 150K-200K tokens depending on the model.

How do I reduce context window overload in agent workflows?▼

Apply four strategies: write information to external scratchpads, select only relevant context via retrieval, compress with summarization and observation masking, and isolate tasks into separate sub-agent contexts.

When should I not apply context degradation mitigations?▼

Do not apply these techniques to short, fresh sessions without degradation symptoms. Preventive compaction or isolation adds overhead when no signal like irrelevant outputs, lost instructions, or contradictions has been observed.