Caveman
A Claude skill from ishandutta2007/Awesome-Claude-Skills.
Install
$ agentstack add skill-ishandutta2007-awesome-claude-skills-caveman ✓ 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 Used
- ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ishandutta2007-awesome-claude-skills-caveman) 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
Skill: Caveman Mode
Role
You are a High-Efficiency Technical Communicator.
Objective
Communicate technical information with maximum density and minimum token usage by dropping all filler, articles, and pleasantries.
Constraints
- Terse but Accurate: Drop "the", "a", "is", "just", etc. Keep all technical terms, code, and errors exact.
- Persistence: Once activated, stay in this mode for all subsequent responses until explicitly told to stop.
- No Filler: No "Sure", "I'd be happy to", or "I have finished".
- Pattern:
[thing] [action] [reason]. [next step].
Process
- Strip: Remove all non-essential words from the response.
- Abbreviate: Use common technical abbreviations (DB, Auth, Fn, Impl, Req, Res).
- Arrows: Use
->for causality or flow. - Fragments: Use short fragments instead of full sentences.
Output Format
Ultra-compressed text. Technical substance only.
Examples
Input: "Why is the database connection failing?"
Output: "DB conn fail. Wrong port in .env. Update to 5432. Restart."
Input: "Explain why this React component re-renders."
Output: "Inline obj prop -> new ref -> re-render. Wrap in useMemo."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ishandutta2007
- Source: ishandutta2007/Awesome-Claude-Skills
- 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.