context-compression

Summarize long conversations into anchored sections to reduce token usage.

Updated May 24, 2026
One-click install
npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill context-compression-fvossebeld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-compression
Source: https://github.com/FVossebeld/agent-skills-for-context-engineering/tree/main/skills/context-compression
Command: npx skills add https://github.com/FVossebeld/agent-skills-for-context-engineering --skill context-compression-fvossebeld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Long agent sessions generate huge context windows; context compression reduces token usage while preserving critical decisions, file references, and next steps.

Core Features & Use Cases

  • Anchored Iterative Summarization with explicit sections to avoid information drift.
  • Opaque Compression for maximum token savings when artifact fidelity is less critical.
  • Regenerative Full Summary for readable, structured refreshes.
  • Probe-based evaluation and a three-phase workflow (research, planning, implementation) to calibrate quality.

Quick Start

Trigger a structured compression pass at the current session boundary to produce an anchored summary.

Frequently Asked Questions about context-compression

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce token usage in long agent sessions without losing critical context?

You can reduce token usage in long agent sessions by applying context compression to summarize history while preserving critical decisions, file references, and next steps. This prevents context window bloat during extended workflows.

What is anchored iterative summarization and how does it prevent information drift?

Anchored iterative summarization is a context compression technique that uses explicit sections to structure summaries over multiple passes. This prevents information drift by maintaining fixed reference points throughout the summarization process.

How do I summarize long conversations for code exploration and debugging workflows?

To summarize long conversations for code exploration and debugging workflows, trigger a structured compression pass at the session boundary to produce an anchored summary that retains critical decisions and file references.

Does context compression support probe-based evaluation for calibrating summary quality?

Yes, context compression supports probe-based evaluation alongside a three-phase workflow (research, planning, implementation) to calibrate summary quality and ensure preserved context fidelity.

When should I use opaque compression over regenerative full summary for token savings?

Use opaque compression for maximum token savings when artifact fidelity is less critical. Choose regenerative full summary instead when you need readable, structured refreshes of the compressed context.