caveman

Compress responses to ultra-compact text while preserving exact code and paths.

1|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/prestarius/jet-skills-stack --skill caveman-prestarius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/prestarius/jet-skills-stack/tree/main/skills/caveman
Command: npx skills add https://github.com/prestarius/jet-skills-stack --skill caveman-prestarius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switch to ultra-compressed communication to cut tokens while preserving accuracy, enabling concise yet correct responses when brevity is required.

Core Features & Use Cases

  • Ultra-compact mode that prioritizes load-bearing detail and eliminates unnecessary preamble, recap, and pleasantries.
  • Keeps critical accuracy: retains all code, commands, paths, and identifiers exactly as provided, even in compressed form.
  • Use Case: when a user requests terse explanations or when token efficiency is essential, such as long back-and-forth interactions or constrained-output tasks.

Quick Start

Activate caveman mode to receive ultra-compact, accurate responses with load-bearing details preserved.

Frequently Asked Questions about caveman

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

FAQPage Schema
How do I get ultra-compact AI responses to cut tokens without losing accuracy?

Ultra-compact AI responses cut tokens by eliminating unnecessary preamble, recaps, and pleasantries while preserving load-bearing details like code, paths, and identifiers exactly as provided.

What is the best way to format prompts for token-efficient communication?

Token-efficient communication is achieved by enforcing strict brevity, avoiding hedging, and retaining exact commands or code. This ensures concise yet correct outputs when long interactions or constrained tasks demand it.

Can I use compressed output mode for long back-and-forth chat interactions?

Compressed output mode works for long back-and-forth interactions by prioritizing load-bearing detail. It removes conversational filler, ensuring precise explanations while maintaining accuracy across extended conversations.

Does ultra-compressed communication preserve exact code and file paths?

Ultra-compressed communication preserves exact code and file paths. It retains all critical identifiers and commands exactly as provided, ensuring functional accuracy even when the surrounding explanation is heavily condensed.

When should I switch to terse explanations for constrained-output tasks?

Switch to terse explanations for constrained-output tasks when token efficiency is essential. Apply ultra-compact communication when brief, precise answers are needed, such as in tutorials or environments with strict output limits.

Are there limitations to using ultra-compact mode for detailed tutorials?

Ultra-compact mode limits detailed tutorials by removing preamble and context. It enforces strict brevity and avoids hedging, which suits token efficiency but may omit conversational explanations needed for complex conceptual onboarding.