caveman-compress
Compress natural language memory files (AGENTS.md, CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, commands, paths, and structure. Compressed version overwrites the original file after backup. Trigger: /skill:caveman-compress FILEPATH or "compress memory file".
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 16
- Forks
- 9
01 前言 Front Matter
- name
- caveman-compress
- description
- Compress natural language memory files (AGENTS.md, CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, commands, paths, and structure. Compressed version overwrites the original file after backup. Trigger: /skill:caveman-compress FILEPATH or "compress memory file".
02 资源文件 9
- 参考文档README.md3.3 KB
- 脚本scripts/__init__.py224 B
- 脚本scripts/__main__.py30 B
- 脚本scripts/benchmark.py2.4 KB
- 脚本scripts/cli.py2.0 KB
- 脚本scripts/compress.py8.4 KB
- 脚本scripts/detect.py4.0 KB
- 脚本scripts/validate.py5.6 KB
- 参考文档SECURITY.md1.5 KB
03 SKILL.md 正文
Caveman Compress
Purpose
Compress natural language files (.md, .txt, .typ, .typst, .tex, extensionless notes) into caveman-speak to reduce input tokens. Compressed version overwrites original only after creating <filename>.original.md backup.
Pi Usage
- Resolve user-provided file path to an absolute path.
- Read this skill's
SECURITY.mdif safety is uncertain. - Prefer the bundled Pi-native helper when available:
cd <directory containing this SKILL.md>
python3 -m scripts <absolute_filepath>
- Helper uses
pi --printwith the user's configured Pi model/provider. It does not call provider SDKs directly and does not call non-Pi model CLIs. - If helper cannot run because Python or Pi CLI is unavailable, do not invent statistics or silently modify files. Explain blocker and offer manual compression using Pi file tools.
- For manual compression:
- Use
readfirst. - Refuse unsupported or sensitive files.
- Write backup as
<filename>.original.mdbefore changing original. - Compress only prose outside protected regions.
- Re-read both files and verify protected content stayed exact.
- Use
The bundled helper is Pi-native: it shells out to pi --print, inheriting the user's Pi model/provider configuration. This package does not call provider SDKs directly, ship provider-specific auth logic, or invoke non-Pi model CLIs.
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 action
- Merge redundant bullets that say same thing differently
- Keep one example where multiple examples show 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,.typ,.typst,.tex, extensionless) - NEVER modify:
.py,.js,.ts,.json,.yaml,.yml,.toml,.env,.lock,.css,.html,.xml,.sql,.sh - Refuse paths or names that look sensitive: credentials, secrets, passwords, tokens, keys,
.ssh,.aws,.gnupg,.kube,.docker - If file has mixed prose + code, compress ONLY prose sections
- If unsure whether something is code or prose, leave unchanged
- Original file is backed up as
FILE.original.mdbefore overwriting - Never compress
FILE.original.md(skip it)
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /skill:technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.