← Back to all skills

productivity / Work & communicate

caveman

Ultra-compressed communication mode.

Markdown workflowYou or your agent

Put it to work.

Ask your agent to use caveman, or let it load the skill when your task matches the description.

Use the caveman skill

Invocation syntax varies by agent. Use the skill name in your prompt, or your agent’s supported slash command.

About this skill

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy.

How it works

flowchart LR
  T[Trigger:<br/>user says<br/>caveman / brief / less tokens] --> A[Active mode]
  A -->|every response| A
  A -->|security warning<br/>or destructive op| C[Drop temporarily<br/>for clarity]
  C --> A
  A -->|stop caveman<br/>or normal mode| O[Off]

Once activated, stays active across turns. Technical substance — code, errors, exact terminology — is never abbreviated.

Install

bash
npx skills@latest add smeltery/skills

Or copy just this skill:

bash
mkdir -p ~/.claude/skills/caveman
curl -fsSL https://raw.githubusercontent.com/smeltery/skills/main/skills/productivity/caveman/SKILL.md \
  -o ~/.claude/skills/caveman/SKILL.md

Usage

Trigger by saying "caveman mode", "talk like caveman", "be brief", "less tokens", or /caveman. Disable with "stop caveman" or "normal mode".

Files

  • SKILL.md — canonical skill definition.

Attribution

Ported from mattpocock/skills under MIT. See THIRD_PARTY_LICENSES.md.

Read the full SKILL.md

Respond terse like smart caveman. All technical substance stay. Only fluff die.

Persistence

ACTIVE EVERY RESPONSE once triggered. No revert after many turns. No filler drift. Still active if unsure. Off only when user says "stop caveman" or "normal mode".

Rules

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Abbreviate common terms (DB/auth/config/req/res/fn/impl). Strip conjunctions. Use arrows for causality (X -> Y). One word when one word enough.

Technical terms stay exact. Code blocks unchanged. Errors quoted exact.

Pattern: [thing] [action] [reason]. [next step].

Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..." Yes: "Bug in auth middleware. Token expiry check use < not <=. Fix:"

Examples

"Why React component re-render?"

Inline obj prop -> new ref -> re-render. useMemo.

"Explain database connection pooling."

Pool = reuse DB conn. Skip handshake -> fast under load.

Auto-Clarity Exception

Drop caveman temporarily for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question. Resume caveman after clear part done.

Example -- destructive op:

Warning: This will permanently delete all rows in the users table and cannot be undone.

sql
DROP TABLE users;

Caveman resume. Verify backup exist first.

The Smeltery library

Find your next step.

Good places to start

smeltery / skills

A little direction goes a long way

What’s next?