caveman

Compresses agent responses into telegraphic style at three intensity levels while preserving technical substance.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill caveman-psiagoleal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/psiagoleal/ai-coding-agent-profiles/tree/main/skills/caveman
Command: npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill caveman-psiagoleal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Every word an AI agent writes is re-sent in the conversation history on every subsequent turn, so verbose filler (greetings, preambles, recaps) multiplies token costs across long sessions. This Skill switches the agent into a compressed communication mode that cuts the fluff while keeping all technical substance intact. ## Core Features & Use Cases - Three intensity levels: lite (no filler, full sentences), full (fragments, dropped articles), and ultra (abbreviations, arrows for causality), switchable at any time and persistent across the session. - Substance protection rules: file paths, commands, error messages, version numbers, and expressions of uncertainty are never shortened or paraphrased. - Auto-clarity fallback: the agent exits compressed mode for security warnings, destructive-action confirmations, and ordered multi-step sequences, then returns to it automatically. - Use Case: During a long debugging session with a tight usage quota, activate full mode so every reply is a terse finding-plus-action line, cutting the per-turn prose cost without losing any diagnostic detail. ## Quick Start Tell the agent to turn on caveman mode at full intensity and keep it active for the rest of the session.

Frequently Asked Questions about caveman

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

FAQPage Schema
How do I reduce token usage in long AI coding sessions?

Activate a compressed response mode so the agent drops greetings, preambles, and recaps, which are re-sent with the history on every turn. Combine this with delegating large file reads to subagents, since tool output dominates the context window.

How do I make an AI agent answer more briefly?

Ask for caveman mode or say "be brief" to switch the agent into a telegraphic register with three levels: lite, full, and ultra. The mode stays active for the whole session until you ask for normal mode again.

Does terse AI output lose technical accuracy?

No, provided the compression only targets form. This mode keeps paths, commands, error messages, and version numbers literal, and preserves uncertainty markers like "unverified" or "probable" instead of converting doubt into assertions.

When should an AI agent not use compressed responses?

Compression should be suspended for security warnings, confirmations of irreversible actions, and ordered multi-step instructions where fragments could invert meaning. Versioned artifacts such as ADRs, commit messages, PR descriptions, and documentation always use full prose.

How much token cost does response compression actually save?

It strongly reduces the agent's own prose, which is a moderate but growing share of the context window. It does not reduce file reads, tool outputs, or images, which dominate usage, so it should be combined with delegation and session pruning.