caveman

Compresses AI responses by removing filler words while preserving technical accuracy.

Updated May 28, 2026
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill caveman-changfengpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/caveman
Command: npx skills add https://github.com/changfengpro/agent-skills --skill caveman-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long, verbose AI responses waste tokens and slow down reading when you only need the technical answer. This Skill cuts token usage by roughly 75% by stripping filler, articles, and pleasantries while keeping all technical substance intact. ## Core Features & Use Cases - Ultra-Compressed Responses: Drops articles, filler words, hedging, and pleasantries; uses fragments, abbreviations, and arrows for causality. - Persistent Mode: Stays active across every response once triggered, until the user says "stop caveman" or "normal mode". - Auto-Clarity Exception: Temporarily reverts to full clarity for security warnings, irreversible action confirmations, and multi-step sequences where fragments could be misread. - Use Case: During a long debugging session, enable caveman mode to get terse, high-density answers like "Bug in auth middleware. Token expiry check use < not <=." instead of paragraph-length explanations. ## Quick Start Tell the AI to use caveman mode for the rest of this conversation to get shorter answers.

Frequently Asked Questions about caveman

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI responses shorter and less verbose?

Enable caveman mode by saying "caveman mode", "be brief", or "less tokens". The AI then drops articles, filler words, and pleasantries while keeping all technical content, code, and error messages exact.

How to reduce token usage in AI chat responses?

Caveman mode cuts token usage by roughly 75% through fragment-style writing, abbreviations like DB/auth/config, and arrows for causality. Technical terms and code blocks remain unchanged, so accuracy is not affected.

Does caveman mode stay active across multiple messages?

Yes, caveman mode persists for every response once triggered and does not drift back to verbose output. It only turns off when the user explicitly says "stop caveman" or "normal mode".

When does caveman mode revert to normal language?

It temporarily drops compression for security warnings, irreversible action confirmations, and multi-step sequences where fragments risk misreading. Full caveman style resumes immediately after the clarity-critical part is done.

Does terse mode affect code blocks or error messages?

No, code blocks remain completely unchanged and error messages are quoted exactly. Only the surrounding prose is compressed; technical terms stay precise and unaltered.