compress

Rewrite markdown and plain-text files into terse form while preserving technical elements.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/lasswellt/blitz-cc --skill compress-lasswellt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compress
Source: https://github.com/lasswellt/blitz-cc/tree/main/skills/compress
Command: npx skills add https://github.com/lasswellt/blitz-cc --skill compress-lasswellt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long markdown and plain-text files consume excessive input tokens when loaded into AI context, increasing costs and reducing efficiency without adding value.

Core Features & Use Cases

  • Terse Rewriting: Converts verbose documentation into compact form by removing articles, fillers, and pleasantries while preserving all technical elements.
  • Structural Preservation: Maintains code fences, URLs, file paths, commands, headings, tables, YAML, and JSON exactly as they appear in the source.
  • Safety & Validation: Creates .original backups before modification and runs structural validation to ensure no content drift occurs during compression.

Quick Start

Use the compress skill to reduce the token size of the file 'docs/architecture.md'.

Frequently Asked Questions about compress

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

FAQPage Schema
How do I reduce token consumption when loading long markdown documentation into AI context?

Markdown token consumption is reduced by rewriting verbose text into a terse form that strips articles and fillers while preserving technical elements like code fences, URLs, and file paths.

What is the best way to compress plain-text research notes without losing structural elements like YAML and JSON?

Compressing plain-text notes without losing structure involves applying a terse output protocol that keeps YAML, JSON, tables, and headings verbatim while condensing the surrounding descriptive text.

How does markdown compression handle code blocks and commands during the token reduction process?

Markdown compression handles code blocks and commands by enforcing structural validation that preserves code fences, commands, and file paths exactly as they appear in the original source file.

Can I safely compress documentation files and still keep the original content as a backup?

Yes, you can safely compress documentation files because the process automatically creates .original backups before modifying the source, ensuring the initial content is always recoverable.

When should I avoid using automated text compression for my skill reference materials?

You should avoid automated text compression when your documentation relies heavily on narrative flow, pleasantries, or verbose explanations that lose meaning when converted into a terse format.

Does compressing markdown files change the relative position or content of headings and tables?

Compressing markdown files does not change the content of headings and tables, as structural validation enforces no content drift, keeping these elements exactly as they appear in the source.