> Quick-reference card for all caveman modes, skills, and commands. "caveman help", "what caveman commands", "how do I use caveman".
npx skills add https://github.com/dbt-labs/docs.getdbt.com --skill caveman-help
Display this reference card when invoked. One-shot — do NOT change mode, write flag files, or persist anything. Output in caveman style.
| Mode | Trigger | What change |
|------|---------|-------------|
| Lite | /caveman lite | Drop filler. Keep sentence structure. |
| Full | /caveman | Drop articles, filler, pleasantries, hedging. Fragments OK. Default. |
| Ultra | /caveman ultra | Extreme compression. Bare fragments. Tables over prose. |
| Wenyan-Lite | /caveman wenyan-lite | Classical Chinese style, light compression. |
| Wenyan-Full | /caveman wenyan | Full 文言文. Maximum classical terseness. |
| Wenyan-Ultra | /caveman wenyan-ultra | Extreme. Ancient scholar on a budget. |
Mode stick until changed or session end.
| Skill | Trigger | What it do |
|-------|---------|-----------|
| caveman-commit | /caveman-commit | Terse commit messages. Conventional Commits. ≤50 char subject. |
| caveman-review | /caveman-review | One-line PR comments: L42: bug: user null. Add guard. |
| caveman-compress | /caveman-compress <file> | Compress .md files to caveman prose. Saves ~46% input tokens. |
| caveman-help | /caveman-help | This card. |
Say "stop caveman" or "normal mode". Resume anytime with /caveman.
Keep user's language by default. User write Portuguese → reply Portuguese caveman. Compress the style, not the language. Technical terms, code, commands, commit types, and exact error strings stay verbatim unless user ask for translation.
Default mode = full. Change it:
Environment variable (highest priority):
export CAVEMAN_DEFAULT_MODE=ultra
Config file (~/.config/caveman/config.json):
{ "defaultMode": "lite" }
Set "off" to disable auto-activation on session start. User can still activate manually with /caveman.
Resolution: env var > config file > full.
Full docs: https://github.com/JuliusBrussee/caveman
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take dbt-labs/caveman-help from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.