CtrlK
BlogDocsLog inGet started
Tessl Logo

juliusbrussee/caveman

Compressed caveman-style prose for AI coding agents — cuts ~65% output tokens while keeping full technical accuracy

96

1.00x
Quality

100%

Does it follow best practices?

Impact

96%

1.00x

Average score across 38 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

This is an excellent skill that embodies its own philosophy — it's concise, actionable, and well-structured. The intensity level table with parallel examples across all six modes is particularly effective, giving Claude unambiguous guidance. The Auto-Clarity section wisely carves out safety exceptions for destructive operations and ambiguous situations, showing thoughtful design around edge cases.

DimensionReasoningScore

Conciseness

The skill is itself a masterclass in conciseness — it practices what it preaches. Every section is tight, no unnecessary explanation of concepts Claude already knows, and the tables/examples are compact yet informative.

3 / 3

Actionability

Highly actionable with concrete before/after examples at each intensity level, explicit pattern templates, specific words to drop, and clear trigger/exit commands. Claude knows exactly what to do and how each level differs.

3 / 3

Workflow Clarity

For a behavioral/communication skill (not a multi-step destructive process), the workflow is crystal clear: activation triggers, persistence rules, intensity switching via /caveman command, auto-clarity exceptions for safety-critical situations, and explicit exit conditions. The Auto-Clarity section serves as a validation checkpoint for when to break the pattern.

3 / 3

Progressive Disclosure

For a single-file skill under 80 lines with no need for external references, the content is well-organized with clear sections (Persistence, Rules, Intensity, Auto-Clarity, Boundaries) that progressively build understanding. No bundle files are needed for this scope.

3 / 3

Total

12

/

12

Passed

Description

100%

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

This is a strong skill description that clearly communicates a unique capability with specific actions, well-defined intensity levels, and comprehensive trigger terms. It uses third person voice appropriately and includes both an explicit 'Use when' clause and an auto-trigger condition. The description is concise yet thorough, making it easy for Claude to distinguish this skill from others.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities: cuts token usage ~75%, maintains technical accuracy, supports specific intensity levels (lite, full, ultra, wenyan-lite, wenyan-full, wenyan-ultra). These are specific, actionable details about what the skill does.

3 / 3

Completeness

Clearly answers both 'what' (ultra-compressed communication that cuts tokens ~75% while keeping technical accuracy, with multiple intensity levels) and 'when' (explicit 'Use when' clause with specific trigger phrases plus auto-trigger condition).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms: 'caveman mode', 'talk like caveman', 'use caveman', 'less tokens', 'be brief', '/caveman', and 'token efficiency'. These are phrases users would naturally say when wanting this behavior.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche — 'caveman mode' communication style with specific intensity levels is unlikely to conflict with any other skill. The trigger terms are unique and specific to this particular behavior.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents