Context Status Skill for Claude
| Show current context status and session health. Use to check how much context has been used, whether auto-compact is approaching, and what state will be preserved.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/pedrohcgs/claude-code-my-workflow --skill context-statusThe instruction itself
8 sections, as written by the author/context-status — Check Session Health
Show the current session status including context usage estimate, active plan,
and preservation state.
What This Skill Shows
- Context usage estimate — Approximate % of context window used
- Active plan — Current plan file and status
- Session log — Most recent session log
- Preservation state — What will survive compaction
Workflow
Step 1: Check Context Monitor Cache
Read the context monitor cache to get the current estimate:
cat ~/.claude/sessions/*/context-monitor-cache.json 2>/dev/null | head -20
Step 2: Find Active Plan
ls -lt quality_reports/plans/*.md 2>/dev/null | head -3
Step 3: Find Session Log
ls -lt quality_reports/session_logs/*.md 2>/dev/null | head -1
Step 4: Report Status
Format the output:
📊 Session Status
─────────────────────────────────
Context Usage: ~XX% (estimated)
Auto-compact: [approaching | not imminent]
📋 Active Plan
File: quality_reports/plans/YYYY-MM-DD_description.md
Status: [draft | approved | in_progress | completed]
Task: [current unchecked task or "none"]
📝 Session Log
File: quality_reports/session_logs/YYYY-MM-DD_description.md
✓ Preservation Check
• Pre-compact hook: [configured | missing]
• Post-compact restore: [configured | missing]
• Session state will be saved before compaction
Notes
- Context % is an estimate based on tool call count
- Actual compaction is triggered by Claude Code automatically
- All important state is saved to disk (plans, logs, MEMORY.md)
Other skills for the same job
different authors, same section of the catalogue
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
How to use it
Take pedrohcgs/context-status from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.