← ClaudeAtlas

context-window-health-checklisted

Assess the health of your current Claude session context and get a clear action recommendation — no technical metrics needed. Use when your session feels long, Claude seems to be forgetting earlier details, or you are unsure whether to continue or start fresh. Triggers: 'check my context', 'context health check', 'is my context running out', 'should I start a new session', 'проверь мой контекст', 'оценка контекста', 'контекст заканчивается'.
KirKruglov/claude-skills-kit · ★ 9 · AI & Automation · score 82
Install: claude install-skill KirKruglov/claude-skills-kit
# Context Window Health Check This skill assesses the health of the current Claude session for non-technical users and delivers a plain-language status with a single, concrete recommendation: keep going, start a handoff, or open a new session. It works entirely in-chat — no token counts, no code, no external tools. **Input:** The user's request (any phrasing); the current session conversation (length, topic diversity, symptom descriptions) **Output:** A structured in-chat response — status indicator (🟢 / 🟡 / 🔴), plain-language explanation, one concrete recommendation, and an optional next-step suggestion. --- ## Language Detection Detect the user's language from their message: - If Russian (or contains Cyrillic): respond in Russian - If English (or other Latin-script language): respond in English - If ambiguous: respond in the language of the trigger phrase used --- ## Instructions ### Step 1: Detect Trigger Intent 1. Identify whether the user is explicitly requesting a context check or implicitly signalling a problem: - **Explicit:** "check my context", "context health check", "is my context running out", etc. - **Implicit:** "Claude, you seem to be forgetting…", "you said something different earlier", "this session is getting long" 2. In both cases proceed to Step 2. 3. If the message is unrelated to session state (e.g., "write me an email") — do not activate this skill; hand off to standard Claude behaviour. ### Step 2: Read Session Signals Analyse the