agentleFS
clearsmogclearsmog/claude-skills/context-status/SKILL.md

context-status

Skill2 starsChanged 9 months agoMITView on GitHub

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.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search common plan locations:

    line 31
  2. Distinctive:

    All important state is saved to disk (plans, logs, MEMORY.md)

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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-status — Check Session Health

Show the current session status including context usage estimate, active plan, and preservation state.

What This Skill Shows

  1. Context usage estimate — Approximate % of context window used
  2. Active plan — Current plan file and status
  3. Session log — Most recent session log
  4. Preservation state — What will survive compaction

Workflow

Step 1: Context usage

There is no on-disk estimate. Claude Code's built-in /context shows actual usage; tell the user to run it for the number.

Step 2: Find Active Plan

Search common plan locations:

ls -lt quality_reports/plans/*.md .planning/*.md plans/*.md 2>/dev/null | head -3

Step 3: Find Session Log

ls -lt quality_reports/session_logs/*.md .planning/logs/*.md 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:   [plan path]
Status: [draft | approved | in_progress | completed]
Task:   [current unchecked task or "none"]

Session Log
File:   [log path]

Preservation Check
  - Pre-compact hook: [configured | missing]
  - Post-compact restore: [configured | missing]
  - Session state will be saved before compaction

Notes

  • Context usage comes from /context
  • Actual compaction is triggered by Claude Code automatically
  • All important state is saved to disk (plans, logs, MEMORY.md)

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.