How do I install the Context skill?

Run npx skillmds@latest add concertonotes/context-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 safe to use?

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

Which AI agents work with Context?

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 free to use?

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

Who published Context?

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

Context by concertonotes — Agent Skill

Name: Context
Rating: 4.666666666666667 (3 reviews)
Author: ConcertoNotes

File contents

Context — Context Window Management

When to Trigger

Context window > 70% capacity
Long conversation with many tool calls
Before starting a large new task in an existing session
User asks to "clean up" or "start fresh"

Process

1. Assess

Estimate current context usage
Identify what's consuming the most context (large file reads, verbose outputs)

2. Preserve

Before compacting, ensure critical state is saved:

Current task and progress → $HARNESS_DIR/sessions/
Key decisions made → note in conversation
Files being worked on → list explicitly

3. Compact

Suggest or trigger compaction with a clear summary:

Summary for compaction:
- Working on: [task description]
- Files modified: [list]
- Current status: [what's done, what remains]
- Key decisions: [important choices made]
- Next step: [what to do after compaction]

4. Resume

After compaction, the resume hook will reload:

Session snapshot from $HARNESS_DIR/sessions/
Project memory from $HARNESS_DIR/memory/
Evolved skills from $HARNESS_DIR/evolved/

Anti-Rationalization

Excuse	Rebuttal	What to do instead
"I still have context left"	Quality degrades well before the hard limit. 70% is the trigger.	Compact proactively. Better to lose 5 min than lose coherence.
"Compacting will lose important context"	That's why you preserve first. The resume hook restores it.	Save state → compact → resume loads snapshot + memory + skills.
"I'll just re-read the files"	Re-reading 5 large files wastes 30%+ of your fresh context.	Summarize key facts before compacting. Read only what you need after.

Evidence Required

Before compacting, confirm ALL of these:

Current task and progress noted in summary
Files being worked on listed explicitly
Key decisions recorded (not just "some decisions were made")
Next step specified clearly
Snapshot written to $HARNESS_DIR/sessions/ (show file name)

Compacting without a summary = guaranteed context loss.

Red Flags

Continuing with 90%+ context without compacting (quality degrades)
Compacting without saving state (lose track of progress)
Re-reading large files after compaction (defeats the purpose)

---name: context-2description: Context window manager. Snapshots session state, compacts conversation, and resumes via hook. Use when context exceeds 70% or a large new task begins.--- # Context — Context Window Management ## When to Trigger - Context window > 70% capacity - Long conversation with many tool calls - Before starting a large new task in an existing session - User asks to "clean up" or "start fresh" ## Process ### 1. Assess - Estimate current context usage - Identify what's consuming the most context (large file reads, verbose outputs) ### 2. Preserve Before compacting, ensure critical state is saved: - Current task and progress → `$HARNESS_DIR/sessions/` - Key decisions made → note in conversation - Files being worked on → list explicitly ### 3. Compact Suggest or trigger compaction with a clear summary: ``` Summary for compaction: - Working on: [task description] - Files modified: [list] - Current status: [what's done, what remains] - Key decisions: [important choices made] - Next step: [what to do after compaction] ``` ### 4. Resume After compaction, the `resume` hook will reload: - Session snapshot from `$HARNESS_DIR/sessions/` - Project memory from `$HARNESS_DIR/memory/` - Evolved skills from `$HARNESS_DIR/evolved/` ## Anti-Rationalization | Excuse | Rebuttal | What to do instead | |--------|----------|-------------------| | "I still have context left" | Quality degrades well before the hard limit. 70% is the trigger. | Compact proactively. Better to lose 5 min than lose coherence. | | "Compacting will lose important context" | That's why you preserve first. The resume hook restores it. | Save state → compact → resume loads snapshot + memory + skills. | | "I'll just re-read the files" | Re-reading 5 large files wastes 30%+ of your fresh context. | Summarize key facts before compacting. Read only what you need after. | ## Evidence Required Before compacting, confirm ALL of these: - [ ] Current task and progress noted in summary - [ ] Files being worked on listed explicitly - [ ] Key decisions recorded (not just "some decisions were made") - [ ] Next step specified clearly - [ ] Snapshot written to `$HARNESS_DIR/sessions/` (show file name) **Compacting without a summary = guaranteed context loss.** ## Red Flags - Continuing with 90%+ context without compacting (quality degrades) - Compacting without saving state (lose track of progress) - Re-reading large files after compaction (defeats the purpose)

Frequently asked questions

Context