Agent skill
context-status
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 this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/context-status-alohays-paper2pr
SKILL.md
/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)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?