Cavecrew
Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
Install
npx skills add kubestellar/console --skill cavecrewgit clone --depth 1 https://github.com/kubestellar/console.git /tmp/console
mkdir -p ~/.claude/skills
cp -r /tmp/console/.agents/skills/cavecrew ~/.claude/skills/cavecrewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Cavecrew = three subagent presets that emit caveman output. Same job as Anthropic defaults (`Explore`, edit-style agents, reviewer); difference is the tool-result they return is compressed, so main context shrinks per delegation. ## When to use cavecrew vs alternatives | Task | Use | |---|---| | "Where is X defined / what calls Y / list uses of Z" | `cavecrew-investigator` | | Same but you also want suggestions/architecture commentary | `Explore` (vanilla) | | Surgical edit, ≤2 files, scope obvious | `cavecrew-builder` | | New feature / 3+ files / cross-cutting refactor | Main thread or `feature-dev:code-architect` | | Review diff, branch, or file for bugs | `cavecrew-reviewer` | | Deep code review with rationale + alternatives | `Code Reviewer` (vanilla) | | One-line answer you already know | Main thread, no subagent | Rule of thumb: **if you'd want the subagent's output in 1/3 the tokens, pick cavecrew. If you'd want prose, pick vanilla.** ## Why this exists (the real win) Subagent tool results get injected into main context verbatim. A vanilla `Explore` that returns 2k tokens of prose costs 2k tokens of main-context budget every time. The same finding from `cavecrew-investigator` returns ~700 tokens. Across 20 delegations in one session that's the difference between context exhaustion and finishing the task. ## Output contracts What main thread can rely on per agent: **`cavecrew-investigator`** ``` <Header>: - path:line — `symbol` — short note totals: <counts>.
Details
- Skill name
cavecrew- Repository
- kubestellar/console
- Path
.agents/skills/cavecrew/SKILL.md- License
- Apache-2.0
- Repo updated
- 18 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Cavecrew skill do?
Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
How do I install the Cavecrew skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add kubestellar/console --skill cavecrew. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Cavecrew popular?
It lives in kubestellar/console, which has 155 GitHub stars and 139 forks, and is included in 1 curated skill list.
Related skills
Caveman
155kubestellar/console
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Caveman Commit
155kubestellar/console
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Caveman Compress
155kubestellar/console
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file
Caveman Stats
155kubestellar/console
Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /caveman-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.
Agentdescent
220ThinkFlowLab/agentdescent
Improve a SKILL.md, agent definition, system prompt, small codebase or host plugin by measuring it against examples and evolving it, rather than rewriting it by hand and hoping. Use whenever the user asks to improve, fix, tune, optimise, "train" or get better results out of one of those -- including when they have no test cases yet, because drafting cases for them to check is step one of the procedure, not a prerequisite for it. AgentDescent runs the edits in parallel and keeps only those that raise held-out reward.
Tech Stack Eval
393shawnpang/startup-founder-skills
When the user needs to choose between technologies, frameworks, or tools — or says "which framework should I use", "compare X vs Y", "should we migrate from X to Y", "what database should I use", "calculate TCO".
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.