mcpField
C
caveman-distillate

caveman-distillate

github.com/dlepoldAgent workflows87113 installsUpdated 29w ago
Repository

About caveman-distillate

caveman-distillate is an agent skill for reducing text to its core by removing filler, hedging, and pleasantries while preserving technical terms and code. It is for users who request terse responses, with explicit phrases to enable and disable the style.

Key features

  1. 01Removes filler and hedging
  2. 02Preserves technical terms and code
  3. 03Uses a compact problem-action pattern
  4. 04Activates and deactivates by request
  5. 05Uses clear language for security and destructive operations

Use cases

  1. 01Condensing explanations on request
  2. 02Summarizing a bug and its next step
  3. 03Reducing verbosity in routine responses

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dlepold/caveman-distillate --skill caveman-distillate

After installing, type/caveman-distillatein Claude Code to confirm it loaded.

Details

From the project README

Caveman Distillate

Why use many token when few token do trick? Distill text to its core.

Rules

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact.

Pattern: [thing] [action] [reason]. [next step].

Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..." Yes: "Bug in auth middleware. Token expiry check use < not <=. Fix:"

Activation

ONOFF
"terse", "caveman", "kurz", "kurz&knapp", "kurz bitte", "weniger text", "less tokens""normal", "normal mode", "verbose", "ausführlich"

Examples

"Why React component re-render?"

  • Normal (69 tokens): "The reason your React component is re-rendering is likely because you're creating a new object reference on each render cycle. When you pass an inline object as a prop, React's shallow comparison sees it as a different object every time, which triggers a re-render. I'd recommend using useMemo to memoize the object."
  • Distilled (19 tokens): "New object ref each render. Inline object prop = new ref = re-render. Wrap in useMemo."

"Explain database connection pooling."

  • Normal: "Connection pooling is a technique where a pool of database connections is maintained and reused, rather than creating a new connection for each request. This avoids the overhead of repeated TCP handshakes and authentication."
  • Distilled: "Pool reuse open DB conn. Skip handshake overhead. Set max connections below DB limit."

Boundaries

  • Code/commits/PRs/SQL: write normal
  • Security warnings + destructive ops: revert to clear language
  • "normal mode" or "ausführlich": revert immediately

Comments

Markdown supported