caveman

Reduce token usage in responses while preserving technical accuracy.

2|1|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/storm-software/shell-shock --skill caveman-storm-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/storm-software/shell-shock/tree/main/.agents/skills/caveman
Command: npx skills add https://github.com/storm-software/shell-shock --skill caveman-storm-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces token usage in conversations while preserving full technical accuracy.

Core Features & Use Cases

  • Intensity-based brevity: switch between lite, full, ultra, and wenyan modes without sacrificing core explanations.
  • Consistent technical detail: maintains accuracy while eliminating filler and hedging.
  • Auto-activation: triggers on common brevity requests or explicit commands like /caveman.

Quick Start

Switch to caveman mode by saying caveman mode or sending /caveman.

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 CLI prompts while keeping technical accuracy?

To reduce token usage, switch to caveman mode by sending the /caveman command or typing "caveman mode" in your dialogue. This activates brevity rules that eliminate filler while preserving full technical accuracy across CLI tasks and interactive conversations.

What intensity levels are available for concise prompt mode-switching?

Concise prompt mode-switching offers four intensity levels: lite, full, ultra, and wenyan. Each mode applies a different strictness level to brevity rules, allowing configurable token reduction while maintaining consistent technical detail across responses.

Does automatic brevity activation trigger without explicit commands?

Automatic brevity activation triggers when it detects common brevity requests in the dialogue, without needing explicit commands. It also supports manual triggering via the /caveman command or the phrase "caveman mode" for immediate mode-switching.

What is the best way to optimize prompt tokens for command-line tasks?

The best way to optimize prompt tokens for command-line tasks is to apply an intensity-based brevity mode like ultra or full. This eliminates conversational filler and hedging while maintaining the precise technical details needed for CLI operations.

Can I use concise mode-switching without losing technical detail in responses?

Concise mode-switching preserves technical detail by targeting only filler and hedging for elimination. Whether using lite, full, ultra, or wenyan modes, the Skill maintains consistent technical accuracy so core explanations remain intact.