skills.rest
wesleysimplicio
wesleysimplicioCOMMUNITY
Explore all skills by this author →
𝕏@wesleysimplicGitHub

caveman

Condense project communications while preserving code blocks and technical terms.

1|Updated May 7, 2026
Search Tags:#token-efficiency#code-blocks#caveman#technical-precision#developer-communication#terse-output
One-click install
npx skills add https://github.com/wesleysimplicio/simplicio-mapper --skill caveman-wesleysimplicio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/wesleysimplicio/simplicio-mapper/tree/main/.skills/caveman
Command: npx skills add https://github.com/wesleysimplicio/simplicio-mapper --skill caveman-wesleysimplicio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces output length while preserving technical precision, including code blocks, API names, and commit references, helping teams save tokens without sacrificing accuracy.

Core Features & Use Cases

  • Always-on caveman style that drops filler while preserving exact technical terms.
  • Supports multiple verbosity levels: lite, full, ultra.
  • Maintains code blocks, API names, and commit/PR references intact.
  • Useful for code reviews, architecture discussions, and technical docs where brevity is valued.

Quick Start

Activate caveman mode by using the command '/caveman full' to receive terse, precise responses.

Frequently Asked Questions about caveman

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

FAQPage Schema
How do I reduce token output while preserving technical precision in code reviews?▼

You can reduce token output by activating a terse output mode that drops filler and pleasantries while preserving exact technical terms, API names, and code blocks intact during code reviews and project communications.

What is caveman mode for developer communication?▼

Caveman mode is a terse output style for developer communication that removes conversational filler and pleasantries while maintaining exact technical terms, commit references, and code blocks for token-efficient project chats.

How do I get concise, exact phrasing for software development summaries?▼

You can get concise, exact phrasing for software development summaries by using verbosity levels like lite, full, or ultra to control output length while ensuring exact API names and technical terms remain unchanged.

Does terse output mode keep code blocks and commit references intact?▼

Yes, terse output mode keeps code blocks, API names, and commit or PR references completely intact, ensuring technical accuracy is preserved while filler text is removed to save tokens.

When should I not use terse output for technical documentation?▼

Avoid using terse output for technical documentation when reader context requires conversational explanations or onboarding flow, as the caveman style intentionally drops pleasantries and filler to prioritize token efficiency.

Related Skills

Explore More Software Engineering Skills→
thimsluggathimslugga

terse-mode

Suppress hedging and preambles to deliver direct code-review responses.

Community
Intermediate
giovannimnzgiovannimnz

caveman

Compresses technical communication to reduce token usage while preserving accuracy.

Community
Intermediate
MRWillisTMRWillisT
7

caveman

Strips filler and hedging from model responses while preserving code blocks and technical terms.

Community
Basic
aryaniyapsaryaniyaps
26

caveman

Reduce token usage with terse, technically accurate communication.

Community
Basic