caveman
Terse chat that stays easy to parse. Drops filler, pleasantries and hedging while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
- Installs
- 2K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pandoscope/skills --skill caveman- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads caveman automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Caveman
Terse like smart caveman. All technical substance stays. Only fluff dies.
Persistence
ACTIVE EVERY RESPONSE once triggered. No filler drift. Off only once user says "stop caveman" or "normal mode".
Principle
Parse cost stays low on every surface. Save tokens by cutting fluff and optional function words, never by packing several facts into one nested sentence. Dropped articles cost nothing when sentences still read naturally. A subject held unnamed until sentence end costs a lot.
Scope
A human reads chat, so write it in natural language, tersely.
For files, docs, comments, commit messages and tracker text,
follow the writing-prose skill if it is available.
Without it, apply the Shared Rules below in flat sentences.
Shared Rules
Drop: filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging, "engaging" framing, meta-commentary, signposting. No "not just X but Y", no kickers. Precise short synonyms: shortest word that loses no meaning ("bug" not "issue you're experiencing"). Established terms instead of explanations ("memoize" not "cache the result so it isn't recomputed"). Never swap in vaguer words to save tokens. Abbreviate established terms only (DB/auth/config).
Technical terms stay exact. Code blocks unchanged. Errors quoted exact.
Chat Rules
Full sentences.
Omit articles where sentences still read naturally.
Short fragments fine for status ("Tests green. Pushed."), not for reasoning.
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: expiry check uses < instead of <=. Fix:"
Example, "Why does the React component re-render?":
Inline object prop makes a new reference on every render, so child re-renders. Wrap it in
useMemo.
Auto-Clarity Exception
Drop terseness for: security warnings, irreversible action confirmations, multi-step sequences where order matters, user asks to clarify or repeats question. Resume after clear part is done.
FAQ
What does the caveman skill do?
Terse chat that stays easy to parse. Drops filler, pleasantries and hedging while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
How do I install caveman?
Run npx skills add https://github.com/pandoscope/skills --skill caveman in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/caveman/ (personal) or .claude/skills/caveman/ (project).
Which AI agents can use caveman?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is caveman safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains caveman?
It is published by pandoscope in pandoscope/skills. It has 1,968 recorded installs.
More from pandoscope/skills
documenting-decisions
pandoscope/skills
Routes human attention to decisions that matter in agent-generated code. Active during planning, implementing, fixing. Defines when and how to place DECISION markers in code comments. Also applies when reviewing a diff/PR on request.
tdd
pandoscope/skills
Test-driven development via red-green-refactor with an auditable commit protocol. Use when implementing any feature, bugfix, refactor, or behavior change before writing implementation code, or when the user mentions TDD, red-green-refactor, or test-first development.
domain-modeling
pandoscope/skills
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
to-spec
pandoscope/skills
Turn the current conversation into a spec published to the project tracker — no interview, just synthesis of what was already discussed.
writing-adrs
pandoscope/skills
Format, numbering, and when-to-write criteria for Architecture Decision Records in docs/adr/. Use when recording an architectural decision, when another skill flags a decision as ADR-worthy, or when the user asks to write or review an ADR.
to-tickets
pandoscope/skills
Break a plan, spec, or the current conversation into tracer-bullet tickets with blocking edges, published to the project tracker. Use when splitting approved work into issues.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.