caveman

Compress AI responses by removing filler and hedging while preserving technical accuracy.

2|Updated Feb 18, 2021
One-click install
npx skills add https://github.com/jinyongp/dotfiles --skill caveman-jinyongp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/jinyongp/dotfiles/tree/main/agents/skills/caveman
Command: npx skills add https://github.com/jinyongp/dotfiles --skill caveman-jinyongp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates conversational filler, pleasantries, and excessive verbosity, allowing you to receive technical information in a highly compressed, efficient format.

Core Features & Use Cases

  • Compressed Response Mode: Strips away hedging and polite endings to focus strictly on technical substance.
  • Context-Aware Formatting: Maintains exactness for code, commands, and errors while simplifying surrounding explanations.
  • Use Case: When debugging complex code, activate this skill to receive only the essential fix and the reasoning, bypassing long-winded explanations that clutter your terminal or chat window.

Quick Start

Activate the caveman skill to force all subsequent AI responses into a terse and compressed format.

Frequently Asked Questions about caveman

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

FAQPage Schema
How do I get compressed AI responses without conversational filler?

To get compressed AI responses, activate a terse output mode that removes pleasantries, hedging, and filler while preserving technical accuracy for debugging and rapid information retrieval. It forces strict exclusion of conversational padding.

Why does AI output include polite endings and hedging when I need technical debugging information?

AI output includes polite endings and hedging due to default conversational padding. Activating a terse compression skill removes this filler, ensuring only technical substance and exact code formatting are returned for debugging.

What is the best way to reduce token usage during rapid information retrieval from AI?

The best way to reduce token usage during rapid information retrieval is to enforce high-density communication patterns that remove filler. This compresses responses to technical substance, maximizing token efficiency without losing accuracy.

How do I format AI status updates to be terse and high-density?

To format AI status updates as terse and high-density, apply a compression mode that strips conversational padding and simplifies explanations while maintaining exactness for code, commands, and errors. This ensures strict adherence to terse output.

Does compressed AI output remove technical accuracy when simplifying explanations?

Compressed AI output does not remove technical accuracy. It strips filler and simplifies surrounding explanations while maintaining exactness for code, commands, and errors, ensuring technical debugging processes preserve critical details.

When should I not use terse AI communication for technical debugging?

You should not use terse AI communication when conversational context, detailed explanations, or polite formatting is required. It is strictly designed for debugging, status updates, and rapid retrieval where token efficiency is prioritized over comprehensive dialogue.