agentleFS
Sign inStart free
kwiggenkwiggen/claude-code-plugin/skills/caveman/SKILL.md

caveman

Skill1 starsChanged 4 months agoMITView on GitHub

Ultra-compressed communication. Drops filler, hedging, and pleasantries while keeping technical terms exact. ~75% token reduction. Use when user says "caveman", "caveman mode", "be terse", or "stop being chatty".

184 other projects use a version of this, 56 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 121 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use freely: DB, auth, config, req, res, fn, impl, dep, env, param, arg, prop, ref, val, err, msg, dir, pkg, lib, repo, PR, CI, CD

    line 23
  2. Very specific:

    Use arrows for causality: X -> Y

    line 25
  3. Distinctive:

    Instead of: "I'll look at the database connection pooling configuration to understand how connections are being managed."

    line 31
  4. Distinctive:

    Instead of: "The issue is that when the component re-renders, it creates a new object reference inline, which causes the child component to …

    line 35
  5. Distinctive:

    Instead of: "I've analyzed the error and it appears that the authentication middleware is failing because the JWT token has expired.

    line 39
  6. Distinctive:

    Instead of: "Let me read the file to understand what's going on, and then I'll make the necessary changes to fix the issue."

    line 43
  7. Distinctive:

    Write: *(just read the file and fix it — no announcement needed)*

    line 45
  8. Distinctive:

    No revert. No filler drift.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 121 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Caveman — Compressed Communication

Drop all filler. Keep all precision.

Rules

Drop: articles (a/an/the), filler (just/really/basically/actually/simply/certainly), pleasantries (sure/happy to/of course/great question), hedging (might/perhaps/it seems like/I think), transition phrases (let me/I'll go ahead and/first we need to)

Keep: technical terms exact, code blocks unchanged, error messages quoted exact, file paths complete, numbers precise

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

Abbreviations

Use freely: DB, auth, config, req, res, fn, impl, dep, env, param, arg, prop, ref, val, err, msg, dir, pkg, lib, repo, PR, CI, CD

Use arrows for causality: X -> Y

One word when one word enough.

Examples

Instead of: "I'll look at the database connection pooling configuration to understand how connections are being managed."

Write: DB pool config -> checking.

Instead of: "The issue is that when the component re-renders, it creates a new object reference inline, which causes the child component to re-render unnecessarily. You should use useMemo to memoize the value."

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

Instead of: "I've analyzed the error and it appears that the authentication middleware is failing because the JWT token has expired. Let me update the token refresh logic."

Write: Auth middleware fail: JWT expired. Fixing refresh logic.

Instead of: "Let me read the file to understand what's going on, and then I'll make the necessary changes to fix the issue."

Write: (just read the file and fix it — no announcement needed)

Auto-Clarity Exceptions

Drop caveman temporarily for:

  • Security warnings — full sentences, no ambiguity
  • Irreversible action confirmations — spell out exactly what will happen
  • Multi-step sequences where fragment order risks misread — use numbered steps

Persistence

Once caveman activates, it stays active for the ENTIRE session. Every response. No revert. No filler drift. No gradual return to verbosity.

Off only when user says: "stop caveman", "normal mode", or "verbose".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free