Context Health Monitor

Detects context degradation signals and triggers state dumps to preserve session quality.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/apsulli/gsd-extended --skill context-health-monitor-apsulli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Context Health Monitor
Source: https://github.com/apsulli/gsd-extended/tree/main/.agent/skills/context-health-monitor
Command: npx skills add https://github.com/apsulli/gsd-extended --skill context-health-monitor-apsulli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI-assisted coding sessions suffer from "Context Rot" — quality degrades as the agent processes more information, leading to repeated failed debugging, circular reasoning, and guesswork. This Skill gives the agent self-monitoring rules to detect these failure patterns and preserve state before quality collapses. ## Core Features & Use Cases - 3-Strike Rule: After 3 failed debugging attempts on the same issue, the agent stops, documents what was tried in .gsd/STATE.md, and recommends a fresh session instead of continuing to flail. - Circular Detection: Recognizes when the same approach is being retried, lists prior attempts, and proposes a fundamentally different approach or a /pause. - Uncertainty Logging: Records uncertain decisions in .gsd/DECISIONS.md with alternatives considered, prompting user guidance rather than guessing. - Use Case: During a long debugging session, the agent fails to fix a test three times. Instead of trying a fourth variation, it writes a structured state dump with attempts, errors, and hypotheses, then hands off cleanly via /pause and /resume. ## Quick Start Ask the agent to monitor its own context health and write a state dump to .gsd/STATE.md if it repeats failed debugging attempts.

Frequently Asked Questions about Context Health Monitor

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

FAQPage Schema
How do I prevent AI coding assistants from degrading in long sessions?▼

Monitor for warning signs like repeated failed debugging, circular approaches, and uncertainty statements. When thresholds are hit, write a structured state dump capturing attempts and hypotheses, then start a fresh session with a clean handoff.

What is context rot in AI agent workflows?▼

Context rot is the quality degradation that occurs as an agent processes more information in a single session. Symptoms include repeating failed fixes, going in circles on the same approach, and increasing uncertainty or backtracking.

How does the 3-strike debugging rule work?▼

If debugging the same issue fails three times, the agent stops attempting fixes, documents what was tried and the errors in .gsd/STATE.md, records its current hypothesis, and recommends starting a fresh session rather than continuing.

Can this skill work with session pause and resume commands?▼

Yes, it integrates with /pause to trigger a proper session handoff and /resume to reload the state dump context. The state dump format ensures the next session restores attempts, hypotheses, and file states.

When should I not rely on automated context monitoring?▼

Self-monitoring depends on the agent recognizing its own failure patterns, which can itself degrade in very long sessions. For critical work, combine it with explicit checkpoints and manual /pause commands at natural milestones.