CtrlK
BlogDocsLog inGet started
Tessl Logo

caveman

Ultra-compressed response mode. Cuts token usage ~75% while keeping full technical accuracy. Use when the user says "caveman", "caveman mode", "be brief", "less tokens", "compress output", or invokes /caveman.

73

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 tight, well-structured instruction skill that delivers concrete rules, patterns, and examples while embodying its own brevity philosophy. It handles destructive-operation safety via an explicit Auto-Clarity Exception; the only soft spots are judgment-dependent exception boundaries and a body length just over the simple-skill threshold.

DimensionReasoningScore

Conciseness

The body is deliberately token-efficient and practices what it preaches ('Strunk at maximum setting. Drop every word that does not add signal.'), assuming Claude's competence with no over-explanation of known concepts, so every token earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout: explicit Drop/Keep-exact/Shape lists, a defined output pattern ('[thing] [verb] [reason]. [next step].'), an abbreviation table, and a concrete before/after bug-summary example plus a destructive-op example with real SQL, covering the common cases.

5 / 5

Workflow Clarity

The mode-toggle behavior is clearly sequenced (activate, apply rules, break out for listed exceptions, resume next turn) and destructive ops get an explicit validation safeguard, but the exception boundary leans on judgment ('signal: brevity hurt comprehension') rather than an explicit checkpoint, leaving a minor gap below the top anchor.

4 / 5

Progressive Disclosure

Well-organized into focused sections (Overview, When to Use, Persistence, Rules, Examples, Auto-Clarity Exception, Pairs With) with content appropriately self-contained and no nested references, though the body slightly exceeds the under-50-line simple-skill exception that would justify a 5.

4 / 5

Total

18

/

20

Passed

Description

90%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, concise description that clearly states both capability and explicit trigger conditions with comprehensive natural-language keywords. The only mild gap is specificity, which describes the mode via two properties rather than a list of discrete actions.

DimensionReasoningScore

Specificity

Names the domain ('Ultra-compressed response mode') and two concrete properties ('Cuts token usage ~75%', 'keeping full technical accuracy'), but does not enumerate a list of several distinct actions, fitting the 'names domain and 1-2 concrete actions' anchor rather than the multi-action anchor at 4.

3 / 5

Completeness

Explicitly answers both 'what' (ultra-compressed response mode that cuts tokens while keeping accuracy) and 'when' with concrete trigger phrases via the 'Use when the user says...' clause, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including the coined term and its synonyms ('caveman', 'caveman mode', 'be brief', 'less tokens', 'compress output') plus an invocation form ('/caveman'), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The 'caveman'/'caveman mode' trigger is a distinctive coined term unlikely to fire for unrelated skills, giving it a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tslateman/duet
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.