caveman

Produce ultra-brief, verbatim responses with one idea per line.

55|4|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/bug-ops/zeph --skill caveman-bug-ops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman
Source: https://github.com/bug-ops/zeph/tree/main/.zeph/skills/caveman
Command: npx skills add https://github.com/bug-ops/zeph --skill caveman-bug-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switch to ultra-compressed, telegraphic output. Use when the user asks for terse, brief, minimal, "caveman", or no-fluff answers; wants responses with articles and filler words dropped; or requests maximally short fragments.

Core Features & Use Cases

  • Drop articles and filler; preserve code blocks, file paths, commands, and identifiers.
  • Telegraphic fragments; one idea per line; minimal punctuation.
  • Use cases: when quick, unambiguous replies are needed in code, docs, or chat workflows.

Quick Start

Ask for a terse answer and expect ultra-brief, verbatim output.

Frequently Asked Questions about caveman

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

FAQPage Schema
How do I get terse, minimal text output without filler words?▼

To get terse, minimal text output, enable telegraphic formatting that drops articles and filler words. This produces ultra-brief responses with one idea per line, minimal punctuation, and preserved code blocks.

What is telegraphic output format and when is it needed?▼

Telegraphic output format is ultra-compressed text that omits articles and filler, presenting fragments with one idea per line. It is needed when quick, unambiguous replies are required for code, docs, or chat workflows.

Can I get brief answers while preserving code blocks and file paths?▼

Yes, brief answers can preserve code blocks. The process drops articles and filler words but strictly preserves code blocks, file paths, commands, and identifiers verbatim for accurate technical reference.

Does ultra-brief output work for documentation tasks?▼

Ultra-brief output works for documentation tasks by providing concise, verbatim responses. It applies telegraphic fragments and one-idea-per-line formatting to docs, ensuring quick, unambiguous technical replies.

What is the best way to format short fragments for chat workflows?▼

The best way to format short fragments for chat workflows is telegraphic, ultra-brief output. This approach drops articles, uses minimal punctuation, and formats one idea per line for maximum brevity and clarity.

Why does dropping articles help with concise coding help?▼

Dropping articles helps with concise coding help by removing filler words that add noise. This telegraphic approach ensures ultra-brief, verbatim responses, preserving only essential information, code blocks, commands, and identifiers.