How do I install the Context Management skill?

Run npx skillmds@latest add rysweet/context-management-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Context Management safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Context Management?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Context Management free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Context Management?

rysweet (@rysweet) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Context Management by rysweet — Agent Skill

Name: Context Management
Author: rysweet

Context Management

Proactive context window management via token monitoring, intelligent extraction, and selective rehydration. Features context health checks, priority-based retention, and recovery guidance. Use when approaching token limits or needing to preserve essential context. Complements /transcripts, /reflect, session checkpoints, and PreCompact hooks.

rysweet 8ce5186 7 files · 8.8 KB Updated Sep 17, 2026

File contents

Context Management Skill

Purpose

Preserve the information needed to continue work across long sessions, compaction, crashes, and handoffs. This skill uses the active agent runtime plus a bundled native shell helper for status and snapshot management.

When to Use

The conversation is getting long or noisy.
A task spans multiple phases, repos, or agents.
You need a compact handoff after a crash or compaction.
You need to rehydrate only requirements, decisions, files touched, validation state, and blockers.

Workflow

Assess context health: identify active goal, constraints, changed files, open todos, validation status, and unresolved questions.
Extract essentials: keep user requirements, decisions, file paths, commands run, failures, fixes, and next actions.
Drop noise: summarize verbose logs and omit repeated command output unless it contains an unresolved error.
Checkpoint: write persistent notes through the active session checkpoint/transcript mechanism when available, or use the bundled helper.
Rehydrate: restore only the minimum context needed for the next action, then verify against repository state before continuing.

Output Shape

Use this structure for handoffs:

## Goal
## User requirements
## Decisions made
## Files changed or inspected
## Validation
## Remaining work
## Blockers

Native Helper

Use the bundled helper for repeatable context status and snapshots:

amplifier-bundle/skills/context-management/scripts/context-management.sh status
amplifier-bundle/skills/context-management/scripts/context-management.sh snapshot "handoff before compaction"
amplifier-bundle/skills/context-management/scripts/context-management.sh list
amplifier-bundle/skills/context-management/scripts/context-management.sh show latest

Snapshots are written to ${AMPLIHACK_CONTEXT_DIR:-$HOME/.amplihack/context-management}.

Native Validation

Use runtime commands and repository checks alongside the helper:

/transcripts recent
/reflect summarize current session context
git --no-pager status --short

If those commands are unavailable, produce the same handoff structure manually from the current conversation and repository state.

---name: context-management-2description: Proactive context window management via token monitoring, intelligent extraction, and selective rehydration. Features context health checks, priority-based retention, and recovery guidance. Use when approaching token limits or needing to preserve essential context. Complements /transcripts, /reflect, session checkpoints, and PreCompact hooks.---# Context Management Skill## PurposePreserve the information needed to continue work across long sessions, compaction, crashes, and handoffs. This skill uses the active agent runtime plus a bundled native shell helper for status and snapshot management.## When to Use- The conversation is getting long or noisy.- A task spans multiple phases, repos, or agents.- You need a compact handoff after a crash or compaction.- You need to rehydrate only requirements, decisions, files touched, validation state, and blockers.## Workflow1. **Assess context health**: identify active goal, constraints, changed files, open todos, validation status, and unresolved questions.2. **Extract essentials**: keep user requirements, decisions, file paths, commands run, failures, fixes, and next actions.3. **Drop noise**: summarize verbose logs and omit repeated command output unless it contains an unresolved error.4. **Checkpoint**: write persistent notes through the active session checkpoint/transcript mechanism when available, or use the bundled helper.5. **Rehydrate**: restore only the minimum context needed for the next action, then verify against repository state before continuing.## Output ShapeUse this structure for handoffs:```markdown## Goal## User requirements## Decisions made## Files changed or inspected## Validation## Remaining work## Blockers```## Native HelperUse the bundled helper for repeatable context status and snapshots:```bashamplifier-bundle/skills/context-management/scripts/context-management.sh statusamplifier-bundle/skills/context-management/scripts/context-management.sh snapshot "handoff before compaction"amplifier-bundle/skills/context-management/scripts/context-management.sh listamplifier-bundle/skills/context-management/scripts/context-management.sh show latest```Snapshots are written to `${AMPLIHACK_CONTEXT_DIR:-$HOME/.amplihack/context-management}`.## Native ValidationUse runtime commands and repository checks alongside the helper:```bash/transcripts recent/reflect summarize current session contextgit --no-pager status --short```If those commands are unavailable, produce the same handoff structure manually from the current conversation and repository state.

Frequently asked questions