CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

caveman-compress

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is caveman-compress in JuliusBrussee/caveman

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill: an executable command verified against the real script bundle, concrete compression rules with before/after examples, explicit validation/retry/backup handling for the destructive overwrite, and a clean one-level-deep reference to its scripts. The only weakness is mild redundancy — the exact-preservation rules for code blocks and inline code are stated twice and could be merged.

Suggestions

Merge the 'CRITICAL RULE' block into the 'Preserve EXACTLY' section — both state that fenced code blocks and inline code must be copied verbatim, and the 'Treat code blocks as read-only regions' bullet restates the same rule a third time.

Clarify or drop the '(no tokens)' annotations in the Process steps (e.g. 'detect file type (no tokens)'), which are cryptic without additional context about why token cost per step matters.

DimensionReasoningScore

Conciseness

Mostly lean: rule lists, exact word lists to remove/preserve, and before/after examples with no padding or explanation of concepts Claude already knows. It sits at the 4 anchor ('efficient; minor instances of over-explanation that could be trimmed') rather than 5 because the code-preservation rules are stated twice — 'Preserve EXACTLY (never modify): Code blocks... Inline code' and again in the 'CRITICAL RULE: Anything inside ``` ... ``` must be copied EXACTLY' block with its redundant 'read-only regions' restatement. Not 3, since the duplication is the only notable inefficiency in an otherwise tight document.

4 / 5

Actionability

Fully executable: 'From the directory containing this SKILL.md, run: python3 -m scripts <absolute_filepath>' is copy-paste ready and verified against the actual bundle (scripts/__main__.py dispatches to cli.main, which takes exactly one filepath argument). The removal word lists ('Articles: a, an, the', 'Filler: just, really, basically...'), preserve lists, file-type boundaries, and two before/after Pattern examples concretely cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Clear 4-step sequence with explicit validation and feedback loops for a destructive operation (overwriting the original): 'validate output (no tokens)', 'if errors: cherry-pick fix... no recompression', 'retry up to 2 times', 'if still failing after 2 retries: report error to user, leave original file untouched', plus 'Original file is backed up as FILE.original.md before overwriting'. The validation cap for destructive operations does not apply — checkpoints and error recovery are explicit, matching the 5 anchor.

5 / 5

Progressive Disclosure

Clear overview with well-organized sections (Purpose, Trigger, Process, Compression Rules, Pattern, Boundaries). The only bundle reference is real and one level deep — 'The compression scripts live in scripts/... search for scripts/__main__.py next to this SKILL.md' — verified to exist, with a sensible fallback search instruction. Compression rules are correctly inline since they are needed at invocation time; nothing that belongs in a separate file is inlined, matching the 5 anchor.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete third-person actions, an explicit trigger clause with a quoted natural phrase, and a distinct niche. The only weakness is limited synonym coverage in the trigger terms. Voice is consistently third person ('Compress', 'Preserves'), so no voice penalty applies.

Suggestions

Add a few natural synonyms to the trigger clause, e.g. 'compress memory file' plus 'shrink/condense CLAUDE.md or .md memory files to save tokens', so users phrasing the request differently still match.

DimensionReasoningScore

Specificity

Multiple specific concrete actions with comprehensive coverage: 'Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format', 'Preserves all technical substance, code, URLs, and structure', 'Compressed version overwrites the original file', 'Human-readable backup saved as FILE.original.md'. This matches the 5 anchor ('multiple specific concrete actions; comprehensive coverage') rather than 4, since the description covers the transformation, preservation guarantees, overwrite behavior, and backup with no meaningful gaps.

5 / 5

Completeness

Clearly answers both what ('Compress natural language memory files... to save input tokens. Preserves all technical substance...') and when with an explicit trigger clause ('Trigger: /caveman-compress FILEPATH or "compress memory file"'). This matches the 5 anchor: concrete trigger phrases are present, so the missing-'Use when' cap of 3 does not apply, and it exceeds the 4 anchor where the 'when' is only implicitly or generically stated.

5 / 5

Trigger Term Quality

Good natural-phrase coverage: 'compress memory file', 'CLAUDE.md', 'todos', 'preferences', and the explicit slash command '/caveman-compress FILEPATH'. It falls at the 4 anchor ('good keyword coverage; a few natural terms missing') rather than 5 because synonym and extension coverage is incomplete — e.g. 'shrink', 'condense', 'reduce tokens', or generic '.md files' are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers: caveman-format token compression of memory files (CLAUDE.md, todos, preferences) is a well-defined slot unlikely to collide with other skills. The unusual 'caveman format' keyword makes mis-triggering for a different skill very unlikely, matching the 5 anchor ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

masweb/waxp-vuebo

Path

.agents/skills/caveman-compress/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.