원클릭으로 Manus에서 모든 스킬 실행

caveman-compress

스타4

포크0

업데이트2026년 5월 14일 20:28

Use when the user invokes /caveman-compress FILEPATH, says "compress memory file", or otherwise asks to compress natural-language memory files (CLAUDE.md, todos, preferences). Rewrites the file into caveman format to save input tokens, preserving all technical substance, code, URLs, and structure. The compressed version overwrites the original; a human-readable backup is saved as FILE.original.md.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

danmestas

danmestas/wardrobe

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Caveman Compress

Purpose

Compress natural language files (CLAUDE.md, todos, preferences) into caveman-speak to reduce input tokens. The compressed version overwrites the original. A human-readable backup is saved as <filename>.original.md.

Trigger

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

Process

The compression scripts live in scripts/ (adjacent to this SKILL.md). If the path is not immediately available, search for scripts/__main__.py next to this SKILL.md.
From the directory containing this SKILL.md, run:

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 the error to the user, leave the original file untouched

Return the result to the 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 a 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
If a file has mixed content (prose + code), compress ONLY the prose sections
If unsure whether something is code or prose, leave it unchanged
The original file is backed up as FILE.original.md before overwriting
Never compress FILE.original.md (skip it)

이 저장소의 다른 Skills

같은 저장소

helland

danmestas/wardrobe

The Pat Helland lens: treat durable data as immutable, append-only facts that carry their own identity and version; and design across service, machine, or org boundaries assuming you cannot have distributed transactions — only idempotent, at-least-once messages that must be reconciled. Apply this on in-place updates and overwrites, "just UPDATE the row," two-phase commit or distributed transactions at scale, exactly-once delivery assumptions, shared mutable state across services, and any data that crosses a boundary of service, machine, org, or time. Trigger even when Helland isn't named — the smell is mutation-in-place and pretending distributed systems can be transactional.

2026-07-184

hickey

danmestas/wardrobe

The Rich Hickey lens: pursue simple (un-braided, one role) over easy (familiar, near-at-hand), decomplect concerns that got tangled together, and separate value, identity, state, and time. Apply this whenever "easy," "convenient," or "it's what we already use" is doing the work of justifying a design; when state is braided into logic, policy into mechanism, or data into behavior; when object-soup would be plainer as data; and when a hard design decision is being made at the keyboard under time pressure instead of thought through first. Trigger even when Hickey isn't named — the smell is complecting, and confusing "easy" with "simple."

2026-07-184

carmack

danmestas/wardrobe

The John Carmack lens: minimize the mutable state you have to reason about, do the simple thing before the clever one, and treat correctness tooling — static analysis, warnings-as-errors, determinism — as non-negotiable. Apply this on sprawling mutable state, "we'll clean it up later," debugging by print- statement whack-a-mole, silenced compiler warnings, nondeterministic or non-reproducible behavior, premature abstraction, perf work that skips measurement, and any "what should we actually work on" prioritization call. Trigger even when Carmack isn't named — the smell is code whose full set of states you can't hold in your head, and effort that isn't ruthlessly focused.

2026-07-184

bellard

danmestas/wardrobe

The Fabrice Bellard lens: build the smallest self-contained thing that fully does the job, get performance from insight instead of hardware, and reuse existing machinery instead of reinventing it. Apply this whenever code is growing dependencies, frameworks, services, or infrastructure to solve a problem that a smaller, sharper implementation could handle — or whenever someone says a thing needs a cluster, a big framework, or a rewrite. Use for size/complexity audits, "do we really need this dependency/service?" questions, performance work where the reflex is to add hardware or caching, green-field "should this be one file or a platform?" decisions, and any moment the answer is trending toward "that's impractical, you'd need X." Trigger even when the user doesn't name Bellard — the smell is scope inflation and reaching for resources over insight.

2026-07-184

vault-autoresearch

danmestas/wardrobe

Use when iteratively researching a topic and filing the synthesis into an Obsidian vault for later ingestion. Output goes to `<vault>/raw/` (NOT directly into wiki pages) so that `vault-ingest` can process it on its own schedule. Triggers: '/vault-autoresearch', 'autoresearch [topic]', 'research [topic] into the vault', 'deep dive into [topic]', 'find everything about [topic] for the vault', 'research and stage'.

2026-07-144

vault-ingest

danmestas/wardrobe

Ingest sources into the Obsidian wiki vault. Reads a source, extracts entities and concepts, creates or updates wiki pages, cross-references, and logs the operation. Supports files, URLs, and batch mode. Triggers on: ingest, process this source, add this to the wiki, read and file this, batch ingest, ingest all of these, ingest this url.

2026-07-144

name	caveman-compress
version	1.0.0
targets	["claude-code"]
type	skill
description	Use when the user invokes /caveman-compress FILEPATH, says "compress memory file", or otherwise asks to compress natural-language memory files (CLAUDE.md, todos, preferences). Rewrites the file into caveman format to save input tokens, preserving all technical substance, code, URLs, and structure. The compressed version overwrites the original; a human-readable backup is saved as FILE.original.md.
category	{"primary":"economy"}
license	{"upstream":"MIT","source":"https://github.com/JuliusBrussee/caveman@63a91ec","path":"skills/caveman-compress/SKILL.md"}

Caveman Compress

Purpose

Trigger

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

Process

The compression scripts live in scripts/ (adjacent to this SKILL.md). If the path is not immediately available, search for scripts/__main__.py next to this SKILL.md.
From the directory containing this SKILL.md, run:

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 the error to the user, leave the original file untouched

Return the result to the 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 a 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
If a file has mixed content (prose + code), compress ONLY the prose sections
If unsure whether something is code or prose, leave it unchanged
The original file is backed up as FILE.original.md before overwriting
Never compress FILE.original.md (skip it)