LaunchKit · 2026
Back to Skills

hz-context-optimizer

This skill should be used when the user asks to "compress context", "summarize conversation history", "implement.

0
299 downloads
by @lidekahdjdhdhsjjs-lang

Setup & Installation

openclaw skills install @lidekahdjdhdhsjjs-lang/hz-context-optimizer

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install hz-context-optimizer

What This Skill Does

Techniques for compressing agent conversation history without losing critical information. Covers three production-ready approaches: anchored iterative summarization, opaque compression, and regenerative full summaries. The core insight is optimizing tokens-per-task rather than tokens-per-request, since overly aggressive compression forces costly re-fetching.

Targeting tokens-per-task instead of tokens-per-request avoids the hidden cost where compression that saves 0.5% more tokens causes 20% more re-fetching, resulting in higher total token spend.

When to use it

  • Compressing a 100+ message debugging session before hitting context limits
  • Tracking which files were modified across a multi-hour coding agent session
  • Designing summarization triggers for codebases over 5M tokens
  • Evaluating compression quality with probe-based recall tests
  • Reducing total token spend on long-running agentic workflows

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Compress this 89,000-token debugging session so the agent can continue without losing context

AGENT
  1. 1Identify the compression trigger point at 70-80% context utilization
  2. 2Define structured summary sections: Session Intent, Files Modified, Decisions Made, Current State, Next Steps
  3. 3Summarize the truncated history span into each explicit section
  4. 4Merge the new summary into any existing structured summary rather than regenerating from scratch
  5. 5Validate retention by running probe questions against the compressed output
OUTPUT

A structured markdown summary preserving the original error, all modified file paths, root cause, test status, and next steps — compressing 89,000 tokens to roughly 300 words