caveman

Transform AI responses into concise caveman-style explanations with configurable intensity levels.

5|4|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/editor-code-assistant/eca-plugins --skill caveman-editor-code-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/editor-code-assistant/eca-plugins/tree/main/plugins/caveman/skills/caveman
Command: npx skills add https://github.com/editor-code-assistant/eca-plugins --skill caveman-editor-code-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultra-compressed communication mode reduces token usage while preserving technical accuracy in software discussions and technical documentation.

Core Features & Use Cases

  • Configurable intensity levels: lite, full, ultra, wenyan-lite, wenyan-full, wenyan-ultra to balance brevity and clarity.
  • Consistent pattern: responses follow a clear [thing] [action] [reason]. [next step] structure for predictability.
  • Auto-triggering by prompts that request token efficiency or brevity to switch modes automatically (with explicit user control).

Quick Start

Enable 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 AI-assisted technical communication without losing accuracy?

Token efficiency in technical communication is achieved by transforming AI responses into concise, structured caveman-style explanations. This format reduces output length while preserving software engineering accuracy, using a predictable [thing] [action] [reason] pattern to maintain clarity.

What is caveman-style technical talk and how does it format code review feedback?

Caveman-style technical talk is an ultra-compressed communication mode that formats code review feedback into a strict [thing] [action] [reason] [next step] structure. This enforces brevity and predictability while retaining all essential technical details.

How do I switch AI responses to brief mode for debugging discussions?

Switch AI responses to brief mode for debugging discussions by sending the /caveman command or mentioning caveman mode. Prompts requesting token efficiency or brevity can also auto-trigger this compressed technical communication format.

Can I configure the intensity of brevity for different software architecture discussions?

You can configure brevity intensity for software architecture discussions using lite, full, and ultra levels. Wenyan-lite, wenyan-full, and wenyan-ultra variants are also available to balance exact compression with required technical clarity.

Does ultra-compressed technical documentation compromise debugging accuracy?

Ultra-compressed technical documentation preserves debugging accuracy by enforcing a consistent structural pattern. It strips conversational filler while retaining precise technical nouns and actions, ensuring software engineering accuracy remains intact despite maximum token reduction.

When should I avoid using terse token-efficient communication for AI assistance?

Avoid terse token-efficient communication for AI assistance when complex software architecture discussions require nuanced elaboration. If debugging context demands extensive reasoning or conversational onboarding, the ultra-compressed format's strict structure may omit necessary explanatory depth.