caveman

Trim excess language from user inquiries while retaining technical terms.

9|Updated May 25, 2026
One-click install
npx skills add https://github.com/wzser/supermatrix --skill caveman-wzser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/wzser/supermatrix/tree/main/platform/skill-master/skills/caveman
Command: npx skills add https://github.com/wzser/supermatrix --skill caveman-wzser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces unnecessary fluff in communication, enhancing clarity and reducing token usage for better efficiency.

Core Features & Use Cases

  • Concise Responses: Removes articles, fillers, and pleasantries from user requests to focus on technical details.
  • Technical Accuracy: Maintains precise technical terms and accurate information.
  • Use Case: In situations where immediate technical understanding is critical and communication should be brief.

Quick Start

Trigger caveman mode by saying "use caveman mode" or "less tokens".

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 during technical troubleshooting sessions?

To reduce token usage during technical troubleshooting, use caveman mode to trim excess language, articles, and fillers from inquiries while preserving all necessary technical details for high-precision information exchanges.

What is the best way to streamline communication for IT support without losing technical accuracy?

Streamlining communication for IT support involves removing pleasantries and unnecessary fluff while retaining precise technical terms, ensuring immediate technical understanding and clarity during critical troubleshooting discussions.

How do I trigger concise responses for high-precision technical discussions?

Trigger concise responses for technical discussions by explicitly instructing the interface to use caveman mode or request less tokens, instantly stripping excess language to focus purely on technical details.

Does removing excess language from tech support chats affect information clarity?

Removing excess language from tech support chats enhances information clarity by eliminating distractions and focusing entirely on the core technical content, which is critical for immediate technical understanding.

When should I not use concise communication modes for technical exchanges?

Avoid using concise communication modes when context, pleasantries, or detailed explanations are necessary for user comprehension, as stripping excess language focuses purely on immediate technical details.