caveman

Compress text responses into caveman-style prose while retaining technical details.

Updated Jan 9, 2020
One-click install
npx skills add https://github.com/tanshunyuan/dotfiles --skill caveman-tanshunyuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/tanshunyuan/dotfiles/tree/main/.agents/skills/caveman
Command: npx skills add https://github.com/tanshunyuan/dotfiles --skill caveman-tanshunyuan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill compresses technical communication to a minimal, caveman-style format, reducing output tokens while preserving full technical accuracy.

Core Features & Use Cases

  • Caveman Communication: Compresses model responses to caveman-style prose, dropping fluff while retaining technical details.
  • Intensity Levels: Offers six intensity levels for varying levels of compression.
  • Auto-Clarity: Automatically switches to normal prose for security warnings, irreversible actions, and when clarity is requested.

Quick Start

/caveman full

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 technical communication without losing information?

Text compression reduces token usage by removing unnecessary words while retaining all technical details. It operates in caveman style, dropping fluff to minimize output tokens while preserving full technical accuracy.

Can I control the intensity of text compression for code simplification?

Yes, text compression offers six intensity levels for varying levels of response reduction. You can select the desired compression level to control how aggressively the text is simplified and tokens are minimized.

Does caveman style text compression automatically switch to normal prose for security warnings?

Auto-clarity automatically switches to normal prose for security warnings, irreversible actions, and when clarity is requested. This ensures critical technical communication remains fully understandable when needed.

What is the best way to compress model responses while preserving technical accuracy?

Compressing model responses to caveman-style prose is the best way to preserve technical accuracy while reducing tokens. It drops fluff and retains all essential technical details for efficient communication.

When should I not use caveman style for technical communication?

You should not use caveman style when conveying security warnings or irreversible actions. The auto-clarity feature detects these critical scenarios and automatically switches to normal prose to ensure clarity.