domains / families / agent-tooling / context-compression

context-compression

combined

This skill should be used when long-running agent sessions need context compression, structured summarization, compaction, token-per-task optimization, or durable handoff summaries that preserve decisions, files, risks, and next actions. When agent sessions generate millions of tokens of conversation history, compression becomes mandatory. The naive approach is aggressive compression to minimize tokens per request.

When to use

• Agent sessions exceed context window limits
• Codebases exceed context windows (5M+ token systems)
• Designing conversation summarization strategies
• Debugging cases where agents "forget" what files they modified
• Building evaluation frameworks for compression quality

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The two copies share the same core philosophy (tokens-per-task, structured summaries, artifact trail) and the same example summary block, but they are not simple reproductions of one another. The muratcankoylan copy adds explicit routing boundaries to other skills (context-optimization, context-degradation, filesystem-context, memory-systems, self-managed-context) and a specific warning against opaque compression when debugging/artifact tracking is critical. The sickn33 copy adds a concrete compression trigger strategy table (fixed threshold, sliding window, importance-based, task-boundary) and a detailed probe-based evaluation framework with specific probe types and a six-dimension evaluation rubric. Because each copy contains material steps and constraints the other lacks, crowning one would hide a real alternative.