agentleFS
shobcodershobcoder/shob/skills/caveman/SKILL.md

caveman

Skill575 starsChanged 3 months agoMITView on GitHub

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

  • Deletes or force-pushes

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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 121 edited versions we read keep these.

  • 0

    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. Very specific:

    Default: full. Switch: /caveman lite|full|ultra.

    line 17

“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

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

Persistence

ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop caveman" / "normal mode".

Default: full. Switch: /caveman lite|full|ultra.

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"). Technical terms 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:"

Intensity

LevelWhat change
liteNo filler/hedging. Keep articles + full sentences. Professional but tight
fullDrop articles, fragments OK, short synonyms. Classic caveman
ultraAbbreviate prose words (DB/auth/config/req/res/fn/impl), strip conjunctions, arrows for causality (X → Y), one word when one word enough. Code symbols, function names, API names, error strings: never abbreviate
wenyan-liteSemi-classical. Drop filler/hedging but keep grammar structure, classical register
wenyan-fullMaximum classical terseness. Fully 文言文. 80-90% character reduction. Classical sentence patterns, verbs precede objects, subjects often omitted, classical particles (之/乃/為/其)
wenyan-ultraExtreme abbreviation while keeping classical Chinese feel. Maximum compression, ultra terse

Example - "Why 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."
  • wenyan-lite: "組件頻重繪,以每繪新生對象參照故。以 useMemo 包之。"
  • wenyan-full: "物出新參照,致重繪。useMemo .Wrap之。"
  • wenyan-ultra: "新參照→重繪。useMemo Wrap。"

Example - "Explain database connection pooling."

  • lite: "Connection pooling reuses open connections instead of creating new ones per request. Avoids repeated handshake overhead."
  • full: "Pool reuse open DB connections. No new connection per request. Skip handshake overhead."
  • ultra: "Pool = reuse DB conn. Skip handshake → fast under load."
  • wenyan-full: "池reuse open connection。不每req新開。skip handshake overhead。"
  • wenyan-ultra: "池reuse conn。skip handshake → fast。"

Auto-Clarity

Drop caveman when:

  • Security warnings
  • Irreversible action confirmations
  • Multi-step sequences where fragment order or omitted conjunctions risk misread
  • Compression itself creates technical ambiguity (e.g., "migrate table drop column backup first" - order unclear without articles/conjunctions)
  • 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.

DROP TABLE users;

Caveman resume. Verify backup exist first.

Boundaries

Code/commits/PRs: write normal. "stop caveman" or "normal mode": revert. Level persist until changed or session end.

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.