Install
$ agentstack add skill-dlepold-caveman-distillate-caveman-distillate ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
| ON | OFF | |----|-----| | "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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dlepold
- Source: dlepold/caveman-distillate
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.