← Back to list
🛠️

Context Health Check

Check real session context metrics; reassess after compaction without guessing model limits.
🛠️ Developer Tools skills By myths-labs Version v3.7.1 Added 2026-09-26 Updated 2026-10-23 Source ↗ Part of Muse & Memory →
7.9Overall rating
0Views
8Downloads
35Stars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "Context Health Check" skill by following the instructions at https://skill123.me/install/context-health-check.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/context-health-check.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v3.7.1 · 991 B
📊 Static rating
7.9/10
Trigger
6.5
Structure
8.0
Workflow
7.5
Content
8.5
Engineering
8.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

The smallest member: reads the client's actual context metrics rather than guessing. A utility, not a workflow.

Context health

Use metrics exposed by the current client for the exact current session. Record

observation time and limitations. Model specifications, user preferences, cached

or cumulative token totals do not establish current context occupancy. A recent

request input is an observation, not a prediction of remaining space.

If reliable metrics are unavailable, report UNKNOWN. Do not estimate occupancy

from turn counts, source-file sizes, model names, or an old static model table.

At observed 80% pressure, save meaningful current-role/Lane deltas, reduce the next

read batch, compact if the client supports it, verify the current checkpoint and

continue the same work. A percentage alone never triggers full Bye, a new Lane,

or a new conversation. After compaction, obtain a fresh observation; prior counts

are stale. Compaction does not prove that all memory survived.

Preserve decisions, user corrections, constraints, unfinished failures, relevant

evidence and the next action. The agent fills the save fields; the user need not

write a template. Save at least every ten interaction rounds if changes remain

unsaved. Only a legacy session without a Lane uses CRASH_CONTEXT.md; never

replace another Lane's state.

Stop for an actual inability to continue, failed recovery, unresolved critical

state contradictions, or an explicit user handoff request. Save confirmed facts

and state what is missing. Do not represent partial recovery as a complete Bye.

Documentation

The smallest member: reads the client's actual context metrics rather than guessing. A utility, not a workflow.

Context health

Use metrics exposed by the current client for the exact current session. Record

observation time and limitations. Model specifications, user preferences, cached

or cumulative token totals do not establish current context occupancy. A recent

request input is an observation, not a prediction of remaining space.

If reliable metrics are unavailable, report UNKNOWN. Do not estimate occupancy

from turn counts, source-file sizes, model names, or an old static model table.

At observed 80% pressure, save meaningful current-role/Lane deltas, reduce the next

read batch, compact if the client supports it, verify the current checkpoint and

continue the same work. A percentage alone never triggers full Bye, a new Lane,

or a new conversation. After compaction, obtain a fresh observation; prior counts

are stale. Compaction does not prove that all memory survived.

Preserve decisions, user corrections, constraints, unfinished failures, relevant

evidence and the next action. The agent fills the save fields; the user need not

write a template. Save at least every ten interaction rounds if changes remain

unsaved. Only a legacy session without a Lane uses CRASH_CONTEXT.md; never

replace another Lane's state.

Stop for an actual inability to continue, failed recovery, unresolved critical

state contradictions, or an explicit user handoff request. Save confirmed facts

and state what is missing. Do not represent partial recovery as a complete Bye.

Score breakdown

Trigger
6.5
Trigger 6.5/10 — The description names the task and a key boundary but lacks multiple trigger phrasings and an explicit when-not-to-run list; the body is dense, precise, and consistent with executable pressure-response steps, verification, and overwrite guardrails.
Structure
8.0
Structure 8/10
Workflow
7.5
Workflow 7.5/10
Content
8.5
Content 8.5/10
Engineering
8.0
Engineering 8/10
Security
9.5
Security 9.5/10