RLM Context Rot Detector

Detect Context Rot symptoms in long-context reasoning sessions.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/Magic8Ballin/rlm-skills --skill rlm-context-rot-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: RLM Context Rot Detector
Source: https://github.com/Magic8Ballin/rlm-skills/tree/main/rlm-context-rot-detector
Command: npx skills add https://github.com/Magic8Ballin/rlm-skills --skill rlm-context-rot-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The RLM Context Rot Detector provides self-monitoring to identify Context Rot symptoms during long-context reasoning and triggers protective measures to preserve output quality.

Core Features & Use Cases

  • Symptom detection: Monitors for circular reasoning, hedging language, missed connections, rushing, and contradictions.
  • Severity scaling: Uses a 0-3 rot severity scale to decide actions.
  • Protective measures: Supports switching to RLM mode, state dumps, or fresh-session recommendations when rot is detected.
  • Self-reinforcement loop: Maintains persistent awareness of the detector across the session to prevent prompt decay.

Quick Start

Start the detector before engaging in large-context reasoning and follow the 3-strike rule to restart sessions when needed.

Frequently Asked Questions about RLM Context Rot Detector

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

FAQPage Schema
What is context rot in long-context LLM reasoning?

Context rot in long-context reasoning refers to output degradation where the LLM exhibits circular logic, hedging, missed connections, and contradictions during extended sessions. It compromises multi-hop reasoning quality and requires active monitoring to detect.

How do I detect context rot symptoms during extended LLM sessions?

To detect context rot symptoms during extended LLM sessions, monitor for circular reasoning, hedging language, rushing, and contradictions. A persistent self-monitoring loop evaluates these symptoms and scales severity from 0 to 3.

When should I use protective measures like state dumps for prompt decay?

State dumps and other protective measures for prompt decay should be used when context rot severity scales to a high level. A 3-strike rule triggers these actions, including switching modes or recommending a fresh session to preserve reasoning quality.

Can I monitor multi-hop reasoning tasks for circular logic automatically?

Yes, you can monitor multi-hop reasoning tasks for circular logic automatically by initiating a self-reinforcement loop before the task. This persistent awareness tracks rot symptoms across the session without manual intervention.

What is the best way to prevent prompt decay in large-context prompts?

The best way to prevent prompt decay in large-context prompts is starting a self-monitoring detector before reasoning begins. It maintains persistent awareness, assesses rot severity, and triggers fresh-session recommendations when decay symptoms appear.