cc-skill:caveman
Claude Code skill · anthropic · active
Switches Claude into ultra-terse mode that cuts out filler words, articles, and pleasantries while keeping all technical accuracy. You get straight answers with 75% fewer tokens, stripped down to pure substance.
Anyone who wants fast, direct technical answers without the conversational padding.
When you say 'caveman mode', 'talk like caveman', 'be brief', 'less tokens', or use /caveman.
- "Switch to caveman mode and explain API rate limiting"
- "Use caveman. Why is my database slow?"
- "Talk like caveman: how does JWT auth work?"
The response drops articles (a, the), filler words (just, really, basically), and pleasantries (sure, happy to), while keeping all technical details intact and using short fragments instead of full sentences.
Deploy this skill
no laptop requiredRun this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.
How this performs
Cloud-automation runs, real outputs, and feedback.
No cloud runs yet for this skill.
Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.
Claude Code skill at /Users/olanrewajukareem/.claude/skills/caveman/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.
>
Local Claude Code use (optional)
Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.
Save this skill to ~/.claude/skills/caveman/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.
{
"source": "global",
"description": ">"
}{
"method": "embed_in_prompt",
"skill_path": "/Users/olanrewajukareem/.claude/skills/caveman/SKILL.md"
}That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.