Communicating Concisely
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
Install
$ agentstack add skill-ganyuanran-aegis-communicating-concisely Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.
Security review
⚠ Flagged1 finding(s); flagged for manual review. · v0.1.0 How review works →
- • Prompt-injection patterns
- • Secret / credential exfiltration
- • Dangerous shell & filesystem operations
- • Untrusted network calls
- • Known-malicious package signatures
- high Destructive filesystem operation.
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 **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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GanyuanRan
- Source: GanyuanRan/Aegis
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.