CtrlK
BlogDocsLog inGet started
Tessl Logo

caveman-compress

Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup. Trigger: /caveman-compress.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/caveman-compress/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 lean, actionable, well-structured skill body: the run command is executable, the destructive operation is guarded by explicit validation, retry, backup, and failure-fallback steps, and all bundle references resolve to real files. The only trims available are consolidating the thrice-stated code-preservation rule and stating the script's execution prerequisites.

DimensionReasoningScore

Conciseness

The body is efficient — dense rule lists and two compact before/after examples with no concept explanations Claude already knows. Not 5 because the code-preservation rule is stated three times ("Preserve EXACTLY: Code blocks (fenced ``` and indented)", the "CRITICAL RULE" block, and the separate inline-code paragraph), which could be trimmed to one.

4 / 5

Actionability

Gives a copy-paste-ready command ("python3 -m scripts <absolute_filepath>" from the SKILL.md directory), a fallback for locating the scripts, and concrete original/compressed example pairs. Not 5 because prerequisites for the script's "call Claude to compress" step (e.g. what CLI/API it invokes) are unstated, leaving a minor gap.

4 / 5

Workflow Clarity

Despite the destructive overwrite, the sequence is explicit with validation checkpoints and a feedback loop: "validate output (no tokens)", "cherry-pick fix with Claude (targeted fixes only)", "retry up to 2 times", and "if still failing after 2 retries: report error to user, leave original file untouched", plus an out-of-tree backup. This matches the anchor with explicit validation, error recovery, and failure fallback — not 4, since no checkpoints are missing.

5 / 5

Progressive Disclosure

Well-organized single-file skill with clear sections (Purpose, Trigger, Process, Compression Rules, Pattern, Boundaries); the only bundle references ("scripts/" and "scripts/__main__.py") are real files one level deep, and the inline compression rules are needed on every run so keeping them in SKILL.md is appropriate. Not 4 because there are no organization gaps or buried references.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific, distinctive description that clearly states what the skill does with concrete file-type examples. Its main weakness is trigger guidance: it names the slash command but never states when a user would naturally want the skill, which caps completeness.

Suggestions

Add a situational trigger clause, e.g. "Use when the user asks to compress, shorten, or shrink CLAUDE.md, memory files, todo lists, or other natural-language files to save input tokens."

Include a few natural synonyms users would say ("shorten", "shrink", "reduce context/tokens") alongside "compress" to broaden trigger-term coverage.

Mention the safety behavior briefly (backup kept, original restored on failure) so the description also conveys when it is safe to invoke.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "Compress a memory file such as CLAUDE.md or a todo list into caveman format", "to save input tokens", "keeping a readable backup". Falls short of 5 because coverage has minor gaps (no mention of validation, retry, or the skip-rules for code files).

4 / 5

Completeness

The "what" is clear (compress memory files into caveman format with a backup), but the only trigger guidance is "Trigger: /caveman-compress", which names the command rather than the situations in which to use it — no "Use when..." or equivalent explicit situational clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "memory file", "CLAUDE.md", "todo list", "compress", "input tokens", "backup". A few natural terms users might say are missing ("shorten", "shrink", "reduce context"), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Caveman format" compression of memory files like CLAUDE.md and todo lists is a clear niche with distinct triggers and minimal conflict risk with other skills. Not 4 because it doesn't overlap meaningfully with generic file-compression or document skills — the token-saving, memory-file framing is unambiguous.

5 / 5

Total

16

/

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
JuliusBrussee/caveman
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.