agentleFS
toonighttoonight/get-shit-done-for-antigravity/.agents/skills/context-health-monitor/SKILL.md

context-health-monitor

Skill952 starsChanged 3 months agoMITView on GitHub

Monitors context complexity and triggers state dumps before quality degrades

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If debugging the same issue fails 3 times:

    line 29
  2. Distinctive:

    If the same approach is being tried again:

    line 41
  3. Distinctive:

    When uncertain about an approach:

    line 50
  4. Very specific:

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

    line 61
  5. Very specific:

    Critical: When any warning signal triggers, the agent must save state BEFORE recommending /pause to the user.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context Health Monitor

Purpose

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

When This Skill Activates

The agent should self-monitor for these warning signs:

Warning Signs

SignalThresholdAction
Repeated debugging3+ failed attemptsTrigger state dump
Going in circlesSame approach tried twiceStop and reassess
Confusion indicators"I'm not sure", backtrackingDocument uncertainty
Session lengthExtended back-and-forthRecommend /pause

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 /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:

## 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 /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 /pause

Why

Sessions can terminate abruptly (usage limits, context limits, network errors). If the agent waits for the user to type /pause, it may never get the chance. By saving first and recommending second, state is always preserved.

Integration

This skill integrates with:

  • /pause — Triggers proper session handoff (includes proactive auto-save)
  • /resume — Loads the state dump context
  • Rule 3 in GEMINI.md — Context Hygiene enforcement

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.