ccr

Compress large data blobs into lossy representations with stdlib-only algorithms.

3|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/broomva/skills --skill ccr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccr
Source: https://github.com/broomva/skills/tree/main/skills/knowledge/ccr
Command: npx skills add https://github.com/broomva/skills --skill ccr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of context window exhaustion by shrinking large blobs like logs, tool outputs, or RAG chunks into compact, lossy views that the model can expand on demand.

Core Features & Use Cases

  • Content-Routed Compression: Automatically applies specialized compactors for JSON skeletons, code outlines, or text head-tail views.
  • Byte-Exact Recovery: Ensures that the original data is cached locally and can be retrieved byte-for-byte, preserving non-UTF-8 characters and specific formatting.
  • Use Case: When a massive log file or a minified JSON response exceeds your context budget, use this skill to compress it into a small handle, allowing the model to inspect the structure and only retrieve the full content when necessary.

Quick Start

Use the ccr skill to compress the file named big-data.json and generate a retrieval handle.

Frequently Asked Questions about ccr

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

FAQPage Schema
How do I compress large JSON payloads to optimize LLM context window usage?

To optimize LLM context window usage, compress large JSON payloads into compact, lossy representations like JSON skeletons using specialized compactors. The original data is cached locally, allowing the model to inspect the structure and retrieve full content via a unique retrieval handle when necessary.

What is the best way to recover original data after lossy compression for LLM context?

Recover original data after lossy compression using a content-addressed local cache that ensures byte-exact recovery. This mechanism preserves non-UTF-8 characters and specific formatting, allowing retrieval of the exact original payload through a unique retrieval handle.

Can I compress code and text formats alongside JSON for LLM context optimization?

Yes, you can compress code and text formats alongside JSON for LLM context optimization. The system automatically applies specialized compactors for code outlines or text head-tail views, routing compression based on the content type to shrink large blobs.

Does context window compression for LLMs require external dependencies?

Context window compression for LLMs does not require external dependencies. The system uses deterministic, stdlib-only compression algorithms to shrink large blobs like logs, tool outputs, or RAG chunks into compact views without needing additional libraries.

When should I use lossy payload compression for LLM context management?

Use lossy payload compression for LLM context management when a massive log file or minified JSON response exceeds your context budget. It shrinks these large blobs into small handles, allowing the model to inspect the structure and expand on demand.