
Communicating Concisely
When you're grinding through a long debugging session or need to cut token usage, this mode strips out articles, filler words, and pleasantries while keeping technical terms and code blocks intact. You trigger it with "caveman mode" or "be brief" and it stays on until you disable it. The skill smartly exits caveman for security warnings or irreversible actions, then resumes after. It's genuinely useful for rapid back and forth where you don't need the polish, though you'll want to turn it off before writing anything user facing. Also claims to reduce false positive content flags on touchy platforms since there's less surface area to trip filters.
- GitHub stars
- 492
- last updated
- Jun 11, 2026
Install
$ npx -y skills add ganyuanran/aegis --skill communicating-concisely --agent claude-codeInstalls into .claude/skills of the current project.
Files
Communicating Concisely
Activation
Triggered by: "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or /communicating-concisely. Once active, applies to EVERY response until explicitly deactivated.
Mode Rules
Drop these categories:
- Articles: a, an, the
- Filler: just, really, basically, actually, simply
- Pleasantries: sure, certainly, of course, happy to
- Hedging and equivocation
Keep exact (never abbreviate or alter):
- Technical terms
- Code blocks
- Error messages (quoted verbatim)
- File paths and line numbers
Structural rules:
- Fragments allowed
- Short synonyms: "fix" not "implement a solution for"
- Abbreviate common terms: DB, auth, config, req, res, fn, impl
- Arrows for causality:
X → Y - One word when one word suffices
- Pattern:
[thing] [action] [reason]. [next step].
Example:
Don't: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
Do: "Bug in auth middleware. Token expiry check uses < not <=. Fix:"
Auto-Clarity Exception
Temporarily exit caveman mode for:
Sponsors
Details
- Repository
- github.com/ganyuanran/aegis
- Category
- Debugging
- License
- MIT
- First seen
- Jun 11, 2026
More from ganyuanran/aegis
All 22- Dispatching Parallel Agents
- Establishing Project Context
- Executing Plans
- Finishing A Development Branch
- First Principles Review
- Goal Framing
- Long Task Continuation
- Receiving Code Review
- Recording Architecture Decisions
- Requesting Code Review
- Subagent Driven Development
- Systematic Debugging
- Test Driven Development
- Update Aegis
- Using Aegis
- Using Git Worktrees
- Verification Before Completion
- Writing Plans
- Writing Skills
- Anti Entropy Governance
- Brainstorming