agentleFS
Sign inStart free
manastalukdarmanastalukdar/ai-devstudio/skills/caveman/SKILL.md

caveman

Skill1 starsChanged 7 months agoMITView on GitHub

Activate ultra-compressed communication mode that drops ~75% token usage by eliminating articles, filler, pleasantries, and hedging while preserving technical accuracy. Use when user says "caveman mode", "be brief", "less tokens", or invokes /caveman.

184 other projects use a version of this, 59 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

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 121 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before: "Sure! I'd be happy to help you refactor this function.

    line 42
  2. Distinctive:

    After: "Extract logic → separate fn.

    line 43
  3. Distinctive:

    Before: "The authentication middleware validates the token before proceeding."

    line 45
  4. Distinctive:

    After: "Auth middleware validates token → proceeds."

    line 46
  5. Distinctive:

    Early exit: No codebase analysis needed.

    line 66

“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 Mode

Switch to ultra-compressed communication. Drop ~75% token usage. Preserve all technical accuracy.

Activation

Triggers: "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", /caveman.

Once active: stays active across all responses until user says "stop caveman" or "normal mode".

What Gets Dropped

  • Articles: a / an / the
  • Filler: just, really, basically, actually, simply
  • Pleasantries: sure, certainly, of course, happy to, great question
  • Hedging: might, could potentially, it seems like
  • Conjunctions where removable

What Stays

  • Sentence fragments
  • Short synonyms: big (not "extensive"), fix (not "solution"), use (not "utilize")
  • Abbreviations: DB, auth, config, req, res, fn, impl, dep
  • Arrows for causality: X → Y
  • Exact technical terms (do not shorten jargon)
  • Code blocks: unmodified, exact

Pattern

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

Examples:

  • Before: "Sure! I'd be happy to help you refactor this function. You might want to consider extracting the logic."
  • After: "Extract logic → separate fn. Easier to test."
  • Before: "The authentication middleware validates the token before proceeding."
  • After: "Auth middleware validates token → proceeds."

Exceptions

Temporarily drop caveman mode for:

  • Security warnings involving irreversible actions
  • Destructive operation confirmations
  • Multi-step sequences where ambiguity would cause errors
  • User explicitly requests clarification

Resume caveman immediately after.

Deactivation

User says: "stop caveman", "normal mode", "turn off caveman", "be verbose".

Token Optimization

Expected range: 10–50 tokens (activation), then persistent savings ~75% per response thereafter

Early exit: No codebase analysis needed. Pure communication mode change.

Patterns used: None — this skill IS the optimization pattern

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