How do I install the Gsd Context Health Monitor skill?

Run npx skillmds@latest add gabrielmoreira/gsd-context-health-monitor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gsd Context Health Monitor safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsd Context Health Monitor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsd Context Health Monitor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsd Context Health Monitor?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsd Context Health Monitor by gabrielmoreira

Name: Gsd Context Health Monitor
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

Context Health Monitor

Overview

Prevent "Context Rot" — the quality degradation that occurs as the agent processes more information in a single session.

When to Use

Monitor for these warning signs throughout the session:

Warning Signs

Signal	Threshold	Action
Repeated debugging	3+ failed attempts	Trigger state dump
Going in circles	Same approach tried twice	Stop and reassess
Confusion indicators	"I'm not sure", backtracking	Document uncertainty
Session length	Extended back-and-forth	Recommend session refresh

Behavior Rules

Rule 1: The 3-Strike Rule

If debugging the same issue fails 3 times:

STOP attempting fixes
Document in .gsd/STATE.md:
- What was tried
- What errors occurred
- Current hypothesis
Recommend user start fresh session
Do NOT continue with more attempts

Rule 2: Circular Detection

If the same approach is being tried again:

Acknowledge the repetition
List what has already been tried
Propose a fundamentally different approach
Or recommend a pause for fresh perspective

Rule 3: Uncertainty Logging

When uncertain about an approach:

State the uncertainty clearly
Document in .gsd/DECISIONS.md:
- The uncertain decision
- Why it's uncertain
- Alternatives considered
Ask user for guidance rather than guessing

State Dump Format

When triggered, write to .gsd/STATE.md:

## Context Health: State Dump

**Triggered**: [date/time]
**Reason**: [3 failures / circular / uncertainty]

### What Was Attempted
1. [Approach 1] — Result: [outcome]
2. [Approach 2] — Result: [outcome]
3. [Approach 3] — Result: [outcome]

### Current Hypothesis
[Best guess at root cause]

### Recommended Next Steps
1. [Fresh perspective action]
2. [Alternative approach to try]

### Files Involved
- [file1.ext] — [what state it's in]
- [file2.ext] — [what state it's in]

Auto-Save Protocol

Critical: When any warning signal triggers, the agent must save state BEFORE recommending a pause to the user. This ensures state persists even if the session hard-terminates.

Steps

Write a state snapshot to .gsd/STATE.md immediately when a threshold is hit
Include at minimum: current phase, current task, last action, next step
Then inform the user of the situation and recommend a pause

Why

Sessions can terminate abruptly (usage limits, context limits, network errors). By saving first and recommending second, state is always preserved.

---name: gsd-context-health-monitordescription: Monitors context complexity and triggers state dumps before quality degrades. Prevents context rot by identifying warning signs like circular debugging or confusion.--- # Context Health Monitor ## Overview Prevent "Context Rot" — the quality degradation that occurs as the agent processes more information in a single session. ## When to Use Monitor for these warning signs throughout the session: ### Warning Signs | Signal | Threshold | Action | |--------|-----------|--------| | Repeated debugging | 3+ failed attempts | Trigger state dump | | Going in circles | Same approach tried twice | Stop and reassess | | Confusion indicators | "I'm not sure", backtracking | Document uncertainty | | Session length | Extended back-and-forth | Recommend session refresh | ## Behavior Rules ### Rule 1: The 3-Strike Rule If debugging the same issue fails 3 times: 1. **STOP** attempting fixes 2. **Document** in `.gsd/STATE.md`: - What was tried - What errors occurred - Current hypothesis 3. **Recommend** user start fresh session 4. **Do NOT** continue with more attempts ### Rule 2: Circular Detection If the same approach is being tried again: 1. **Acknowledge** the repetition 2. **List** what has already been tried 3. **Propose** a fundamentally different approach 4. **Or** recommend a pause for fresh perspective ### Rule 3: Uncertainty Logging When uncertain about an approach: 1. **State** the uncertainty clearly 2. **Document** in `.gsd/DECISIONS.md`: - The uncertain decision - Why it's uncertain - Alternatives considered 3. **Ask** user for guidance rather than guessing ## State Dump Format When triggered, write to `.gsd/STATE.md`: ```markdown ## Context Health: State Dump **Triggered**: [date/time] **Reason**: [3 failures / circular / uncertainty] ### What Was Attempted 1. [Approach 1] — Result: [outcome] 2. [Approach 2] — Result: [outcome] 3. [Approach 3] — Result: [outcome] ### Current Hypothesis [Best guess at root cause] ### Recommended Next Steps 1. [Fresh perspective action] 2. [Alternative approach to try] ### Files Involved - [file1.ext] — [what state it's in] - [file2.ext] — [what state it's in] ``` ## Auto-Save Protocol **Critical:** When any warning signal triggers, the agent must save state BEFORE recommending a pause to the user. This ensures state persists even if the session hard-terminates. ### Steps 1. **Write** a state snapshot to `.gsd/STATE.md` immediately when a threshold is hit 2. **Include** at minimum: current phase, current task, last action, next step 3. **Then** inform the user of the situation and recommend a pause ### Why Sessions can terminate abruptly (usage limits, context limits, network errors). By saving first and recommending second, state is always preserved.

Frequently asked questions

Gsd Context Health Monitor