agentleFS
JuankCadavidJuankCadavid/akili-specs/.claude/skills/caveman/SKILL.md

caveman

Skill12 starsChanged 14 days agoMITView on GitHub

Trigger: token efficiency, 'less tokens', 'be brief', caveman mode, inter-agent communication in /akili-execute and /akili-test. Ultra-compressed communication style (~65% fewer output tokens, measured upstream) for TRANSIENT agent output only — technical substance stays, fluff dies. Never applies to persistent documents (cognitive-doc-design territory) or HITL approval gates.

185 other projects use a version of this, 137 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, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 125 edited versions we read keep these.

  • 1

    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:

    No self-reference: never announce or name the style, no "caveman mode on".

    line 39

“Common” is measured: kept by at least 6 in 10 of the 125 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 — Token-Economy Communication for Transient Agent Output

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

In AKILI, output-token waste is MUDA (see kaizen). This skill is the preventive tactic: it compresses the style of transient agent output — the chatter nobody rereads — while the documents humans live with stay under cognitive-doc-design.

Scope Contract (the AKILI boundary — read first)

OutputCaveman?Level
Inter-agent messages (Leader ↔ Implementer / Reviewer / Tester): task briefs, completion reports, status relays — the verbatim zones below always win (Reviewer/Tester reports relay unchanged)Yesfull
Progress narration and status lines shown to the user mid-runYeslite
Persistent artifacts: PRD, TRD, requirements.md, design.md, tasks.md, execution.md audit entries, test-report.md, PR descriptions, Kaizen logNo — cognitive-doc-design owns artifactsoff
HITL approval gates: option menus, blocker questions, end-of-task summaries the user decides onNo — decision quality > token savingsoff
Security warnings, irreversible-action confirmations, Pivot Protocol blockersNo (upstream Auto-Clarity rule)off
Verbatim evidence: requirement text and Given/When/Then acceptance criteria quoted in briefs/slices, error strings, Reviewer findings passed to rework, test output, code, commandsNever compressed or paraphrasedn/a

One sentence to remember: cognitive-doc-design owns artifacts; caveman owns transient agent output.

Rules (upstream, preserved)

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). No tool-call narration, no decorative tables/emoji, no dumping long raw error logs unless asked — quote shortest decisive line. Standard tech acronyms OK (DB/API/HTTP); never invent abbreviations (cfg/impl/req/res/fn) — tokenizer splits them same as full word: zero tokens saved, reader still decodes. No causal arrows (→) — own token, saves nothing. Technical terms exact. Code blocks unchanged. Errors quoted exact.

Preserve the user's dominant language — compress the style, not the language (Spanish user gets Spanish caveman). Keep technical terms, code, API names, CLI commands, commit-type keywords, and exact error strings verbatim.

No self-reference: never announce or name the style, no "caveman mode on".

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

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

Intensity Levels (upstream; AKILI uses lite and full)

LevelWhat changes
liteNo filler/hedging. Keep articles + full sentences. Professional but tight
fullDrop articles, fragments OK, short synonyms. No tool-call narration, no decorative tables/emoji, no raw log dumps. Standard acronyms OK; no invented abbreviations
ultraStrip conjunctions when unambiguous; one word when one word enough. Not used by AKILI defaults — allowed only if the user explicitly asks
wenyan-*Classical-Chinese register variants from upstream; not used by AKILI

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."

Auto-Clarity (upstream, preserved and extended)

Drop caveman when: security warnings; irreversible-action confirmations; multi-step sequences where fragment order risks misread; compression itself creates ambiguity ("migrate table drop column backup first" — order unclear); the user asks to clarify or repeats a question. AKILI extension: every HITL pause is an Auto-Clarity zone by definition. Resume caveman after the clear part is done.

AKILI-SPECS Integration

AKILI momentThis skill's job
/akili-executeLeader→Implementer briefs, Implementer completion reports, Leader relay of Reviewer feedback: full. Progress lines: lite. execution.md audit entries, PR descriptions, HITL summaries and Pivot blockers: off
/akili-testLeader→Tester context slices and Tester structured reports: full. test-report.md and PRODUCT_BUG escalations to the user: off
Every other commandNot loaded. Documents and user-facing methodology output are cognitive-doc-design territory
kaizenToken savings from compressed inter-agent chatter are measurable MUDA reduction; a retrospective may cite them

Adaptation rules: the Structured Feedback rule of /akili-execute wins over compression — Reviewer FAIL reports pass to the next Implementer unchanged, never paraphrased; a Tester's STATUS: lines and evidence quotes are verbatim zones; when in doubt whether output is transient or persistent, treat it as persistent (off).

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.