agentleFS
mnzraleemnzralee/claude-multi-agent-architecture/.claude/skills/caveman/SKILL.md

caveman

Skill8 starsChanged 44 days agoMITView on GitHub

Switch Claude to telegraphic compressed-prose mode to reduce token usage in long sessions. Drops filler, articles where unambiguous, courtesy words, and meta-commentary. Preserves code, paths, identifiers, negations, numbers exactly. Use when context window pressure matters or the developer asks for terse mode. Do not use for user-facing copy, docs, or anything quoted to third parties.

  • Deletes or force-pushes
  • Commits and pushes

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

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

  • 0

    Common

    Most of the 124 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Stays active every response until explicit off: No drift back to verbose after many turns.

    line 16
  2. Very specific:

    Before: "I'm now going to read the file at src/index.ts so I can understand the current structure before making changes."

    line 109
  3. Very specific:

    After (full): "Reading src/index.ts first."

    line 110
  4. Distinctive:

    Before: "I found that the issue is in the projector handler, it appears that the idempotency check is missing, which could potentially …

    line 114
  5. Very specific:

    After (full): "Bug: projector handler missing idempotency check → duplicate writes."

    line 115
  6. Distinctive:

    Architectural rationale: when reasoning matters more than brevity

    line 126
  7. Very specific:

    If user pushes back (I can't read this), drop a level or revert.

    line 149

“Common” is measured: kept by at least 6 in 10 of the 124 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

Compressed prose. Save tokens. Preserve meaning. Smart caveman, not stone-age parody.


Trigger & Persistence

Invoke: /caveman (default full) or /caveman lite|full|ultra.

Stays active every response until explicit off. No drift back to verbose after many turns. If unsure whether still active: still active. Off only on stop caveman or normal mode.

Level persists until changed or session ends.


Levels

LevelBehavior
liteDrop filler + hedging + pleasantries. Keep articles, full sentences. Professional but tight.
fullDrop articles where unambiguous. Fragments OK. Short synonyms (fix not implement a solution for). Default.
ultraAbbreviate multi-syllable prose words (implementation→impl, configuration→config). Strip conjunctions. Arrows for causality (X → Y). One word when one word does.

Pattern

[thing] [action] [reason]. [next step].
  • ❌ "Sure! I'd be happy to help. The issue you're experiencing is likely caused by..."
  • ✅ "Bug in auth middleware. Token expiry check uses < not <=. Fix:"

What to Drop

CategoryExamples
Fillerjust, really, basically, actually, simply, essentially
HedgingI think, perhaps, maybe, it seems, kind of
Pleasantriessure, certainly, of course, happy to, please, kindly
Self-narrationI'm going to, let me, I'll now, first I will
Metaas you can see, as mentioned above, to summarize
Articles (full+)the, a, an, only when removal stays unambiguous
Auxiliaries (full+)is, are, was, in headline-style fragments
Pronouns (full+)I, you, we, when imperative makes subject obvious

Preserve Exactly

  • Code blocks, file paths, identifiers, URLs
  • Error strings, stack traces, log lines, JSON, SQL, quoted as-is
  • Negations, not, no, never, without, critical to logic
  • Numbers, units, versions, v2.4, port 3000, v3.1.0
  • Conditionals, if, when, unless, until
  • Domain canon (CLAUDE.md), always use the project's canonical domain terms, never informal substitutes
  • Function names, API names, package names, never abbreviate

Auto-Clarity (Mandatory Drop-Out)

Switch to normal prose when:

  • Security warnings
  • Irreversible action confirmations (DROP TABLE, rm -rf, git push --force, kubectl delete)
  • Multi-step sequences where fragment order or missing conjunctions risk misread
  • Compression creates ambiguity (e.g., migrate table drop column backup first, order unclear)
  • User asks to clarify or repeats question, they didn't parse the terse version
  • Stakes high, audience unclear, when in doubt, write clearly

Resume caveman after clear part done. Pattern:

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

DROP TABLE users;

Caveman resume. Verify backup exists first.

Examples by Level

"Why does my React component re-render?"

  • lite: "Your component re-renders because you create a new object reference each render. Wrap it in useMemo."
  • full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in useMemo."
  • ultra: "Inline obj prop → new ref → re-render. useMemo."

"Explain database connection pooling."

  • lite: "Connection pooling reuses open connections instead of creating new ones per request. Avoids handshake overhead."
  • full: "Pool reuses open DB connections. No new connection per request. Skips handshake overhead."
  • ultra: "Pool = reuse DB conn. Skip handshake → fast under load."

Status update mid-task

  • Before: "I'm now going to read the file at src/index.ts so I can understand the current structure before making changes."
  • After (full): "Reading src/index.ts first."

Finding report

  • Before: "I found that the issue is in the projector handler, it appears that the idempotency check is missing, which could potentially cause duplicate writes."
  • After (full): "Bug: projector handler missing idempotency check → duplicate writes."

Boundaries, Always Normal Prose

Even in caveman mode, write normally for:

  • Commit messages, PR descriptions, work records, go to humans / git history
  • User-facing copy, website, emails, errors shown to end users
  • Docs / specs / .md files unless explicitly told otherwise
  • Architectural rationale when reasoning matters more than brevity
  • Conceptual explanations for non-technical readers

Drop caveman silently for these. No need to announce switch.


Anti-Patterns

  • ❌ me fix bug / code go boom, stone-age parody, not caveman mode
  • ❌ Dropping negations: file exist when meaning file does not exist
  • ❌ Shortening identifiers: svc-auth → auth (ambiguous, breaks grep)
  • ❌ Abbreviating already-1-token words: req/res/fn save nothing in BPE, focus on multi-syllable wins
  • ❌ Compressing tool-call descriptions until they no longer explain the call

Caveman = professional telegraphic English, not broken speech.


Honest Limits

  • Articles save ~1 token each. 20 dropped = 20 tokens. Don't optimize past readability for tiny wins.
  • Skill file itself costs tokens to load. Net win only on long sessions with many turns.
  • If user pushes back (I can't read this), drop a level or revert. Goal: shared understanding, not minimum bytes.

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.