C

compress

by @juliusbrusseev
4.7(6)

将自然语言文件压缩为Caveman风格以减少输入Token,原文件备份为.original.md

automationproductivitydocumentationcompressionworkflow-automationGitHub
安装方式
npx skills add https://github.com/juliusbrussee/caveman --skill compress
compare_arrows

Before / After 效果对比

1
使用前

文档包含大量冗余表述和填充词,消耗过多输入Token,上下文窗口空间浪费,处理成本高昂

使用后

自动压缩文档为Caveman极简风格,保留核心信息,Token使用量减少60%,降低处理成本

SKILL.md

compress

Caveman Compress

Purpose

Compress natural language files (CLAUDE.md, todos, preferences) into caveman-speak to reduce input tokens. Compressed version overwrites original. Human-readable backup saved as <filename>.original.md.

Trigger

/caveman:compress <filepath> or when user asks to compress a memory file.

Process

The compression scripts live in caveman-compress/scripts/ (adjacent to this SKILL.md). If the path is not immediately available, search for caveman-compress/scripts/__main__.py.

Run:

cd caveman-compress && python3 -m scripts <absolute_filepath>

  • The CLI will:

  • detect file type (no tokens)

  • call Claude to compress

  • validate output (no tokens)

  • if errors: cherry-pick fix with Claude (targeted fixes only, no recompression)

  • retry up to 2 times

  • if still failing after 2 retries: report error to user, leave original file untouched

  • Return result to user

Compression Rules

Remove

  • Articles: a, an, the

  • Filler: just, really, basically, actually, simply, essentially, generally

  • Pleasantries: "sure", "certainly", "of course", "happy to", "I'd recommend"

  • Hedging: "it might be worth", "you could consider", "it would be good to"

  • Redundant phrasing: "in order to" → "to", "make sure to" → "ensure", "the reason is because" → "because"

  • Connective fluff: "however", "furthermore", "additionally", "in addition"

Preserve EXACTLY (never modify)

  • Code blocks (fenced ``` and indented)

  • Inline code (backtick content)

  • URLs and links (full URLs, markdown links)

  • File paths (/src/components/..., ./config.yaml)

  • Commands (npm install, git commit, docker build)

  • Technical terms (library names, API names, protocols, algorithms)

  • Proper nouns (project names, people, companies)

  • Dates, version numbers, numeric values

  • Environment variables ($HOME, NODE_ENV)

Preserve Structure

  • All markdown headings (keep exact heading text, compress body below)

  • Bullet point hierarchy (keep nesting level)

  • Numbered lists (keep numbering)

  • Tables (compress cell text, keep structure)

  • Frontmatter/YAML headers in markdown files

Compress

  • Use short synonyms: "big" not "extensive", "fix" not "implement a solution for", "use" not "utilize"

  • Fragments OK: "Run tests before commit" not "You should always run tests before committing"

  • Drop "you should", "make sure to", "remember to" — just state the action

  • Merge redundant bullets that say the same thing differently

  • Keep one example where multiple examples show the same pattern

CRITICAL RULE: Anything inside ... must be copied EXACTLY. Do not:

  • remove comments

  • remove spacing

  • reorder lines

  • shorten commands

  • simplify anything

Inline code (...) must be preserved EXACTLY. Do not modify anything inside backticks.

If file contains code blocks:

  • Treat code blocks as read-only regions

  • Only compress text outside them

  • Do not merge sections around code

Pattern

Original:

You should always make sure to run the test suite before pushing any changes to the main branch. This is important because it helps catch bugs early and prevents broken builds from being deployed to production.

Compressed:

Run tests before push to main. Catch bugs early, prevent broken prod deploys.

Original:

The application uses a microservices architecture with the following components. The API gateway handles all incoming requests and routes them to the appropriate service. The authentication service is responsible for managing user sessions and JWT tokens.

Compressed:

Microservices architecture. API gateway route all requests to services. Auth service manage user sessions + JWT tokens.

Boundaries

  • ONLY compress natural language files (.md, .txt, extensionless)

  • NEVER modify: .py, .js, .ts, .json, .yaml, .yml, .toml, .env, .lock, .css, .html, .xml, .sql, .sh

  • If file has mixed content (prose + code), compress ONLY the prose sections

  • If unsure whether something is code or prose, leave it unchanged

  • Original file is backed up as FILE.original.md before overwriting

  • Never compress FILE.original.md (skip it)

Weekly Installs6.2KRepositoryjuliusbrussee/cavemanGitHub Stars24.5KFirst Seen5 days agoSecurity AuditsGen Agent Trust HubPassSocketPassSnykFailInstalled oncursor5.5Kcodex5.3Kgithub-copilot5.2Kopencode5.2Kantigravity5.1Kgemini-cli5.0K

用户评价 (0)

发表评价

效果
易用性
文档
兼容性

暂无评价

统计数据

安装量46.4K
评分4.7 / 5.0
版本
更新日期2026年7月4日
对比案例1 组

用户评分

4.7(6)
5
67%
4
33%
3
0%
2
0%
1
0%

为此 Skill 评分

0.0

兼容平台

🔧Claude Code

时间线

创建2026年4月14日
最后更新2026年7月4日
🎁 Agent 知识卡片
调研问卷