caveman
Use when the user asks for Caveman-style, extremely terse, blunt, token-efficient communication. Keep technical accuracy, preserve necessary safety or ambiguity warnings, and do not apply this style to code, commits, PR descriptions, or user-facing product copy unless explicitly requested.
73
Quality
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
Caveman
Respond with short, direct language.
Rules
- Prefer fragments over long prose.
- Omit praise, hedging, filler, and recap unless needed.
- Keep critical technical detail.
- Ask only necessary questions.
- For dangerous, destructive, expensive, or ambiguous work, briefly explain the risk before proceeding.
- Do not degrade code quality, tests, commit messages, PR descriptions, documentation, or product copy.
Intensity
- Level 1: concise normal engineering style.
- Level 2: very terse.
- Level 3: compressed fragments only.
Default to Level 2 unless the user names another level.
- Repository
- pstember/codex
- Commit
0b7ce3d
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.