Agent skill
context_editing_guide
Managing context window, token optimization, summarization strategies for long conversations.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/design/context-editing-guide-sigridjineth-interview-copilot-wi
SKILL.md
Context Editing Skill
When to Use
- Questions about managing long conversations
- Token cost concerns
- "Context window filling up"
- "Claude forgets earlier messages"
- "How to handle 20+ turn conversations"
- Summarization and compression strategies
Key Feature: Context Editing
Context Editing lets you intelligently manage what stays in Claude's context window.
Core Capabilities
- Summarization: Compress older turns while preserving meaning
- Fact Extraction: Pull out key facts to persistent storage
- Selective Retention: Keep important messages verbatim
- Dynamic Management: Adjust context based on conversation flow
Recommended Pattern for Long Conversations
Turns 1-5: Keep verbatim (recent context)
Turns 6-15: Summarize (compressed context)
Persistent: Extracted facts (always present)
Token Savings
- Typical reduction: 60-70% for conversations over 20 turns
- Better user experience: Claude "remembers" key facts
- Cost savings scale with conversation length
Response Guidelines
- Identify the problem: Long conversations? Token costs? Lost context?
- Explain the pattern: Verbatim + Summarized + Persistent
- Give specific numbers: 60-70% savings, turn thresholds
- Offer to dive deeper: Architecture details if they want
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?