/communicating-concisely
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
$ npx -y skills add GanyuanRan/Aegis --skill communicating-concisely --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/communicating-concisely
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
SKILL.md
communicating-concisely.SKILL.mdname: communicating-concisely
description: "Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer."
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:
1. Security warnings 2. Irreversible action confirmations 3. Multi-step sequences where fragment order risks misread 4. User asks for clarification or repeats their question
After the clear section finishes, resume caveman. Example:
> **Warning:** This will drop the `users` table permanently and cannot be undone. > ```sql > DROP TABLE users; > ``` > Caveman resume. Verify backup exists first.
Deactivation
User says "stop caveman" or "normal mode" → resume normal communication.
Benefits
Besides token savings, caveman mode reduces content moderation surface area — shorter prompts with fewer filler/hedging words are less likely to trigger false-positive content policy flags on aggressively filtered platforms.
Red Flags
- Never drop technical precision for brevity
- Never abbreviate security-relevant terms
- Never use caveman for user-facing documentation or commit messages
Read more
name: communicating-concisely description: "Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer."
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:
1. Security warnings 2. Irreversible action confirmations 3. Multi-step sequences where fragment order risks misread 4. User asks for clarification or repeats their question
After the clear section finishes, resume caveman. Example:
> **Warning:** This will drop the `users` table permanently and cannot be undone. > ```sql > DROP TABLE users; > ``` > Caveman resume. Verify backup exists first.
Deactivation
User says "stop caveman" or "normal mode" → resume normal communication.
Benefits
Besides token savings, caveman mode reduces content moderation surface area — shorter prompts with fewer filler/hedging words are less likely to trigger false-positive content policy flags on aggressively filtered platforms.
Red Flags
- Never drop technical precision for brevity
- Never abbreviate security-relevant terms
- Never use caveman for user-facing documentation or commit messages
Aegis Method Pack Make your AI coding agent trustworthy: fewer reworks, safer changes, proof before "done". English · 中文 · Fast-Track Playbook · 速通秘籍 Stop babysitting your agent.
Other skills on aegis.
- /anti-entropy-governance
Use when retiring old logic, collapsing duplicate owners, removing fallbacks, or touching schema, persistence, or source-of-truth boundaries while deciding whether to delete old paths, retain compatibility, or stop for confirmation.
Open skill - /brainstorming
Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.
Open skill - /dispatching-parallel-agents
Use when facing 2+ independent tasks without a written plan that can be worked on without shared state or sequential dependencies. Planned tasks in the current session use subagent-driven-development.
Open skill - /establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
Open skill - /executing-plans
Use when executing a written implementation plan across sessions or with review checkpoints. For same-session execution with independent tasks, use subagent-driven-development instead.
Open skill - /finishing-a-development-branch
Use when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly requests merge, PR, or branch lifecycle handling.
Open skill