Caveman Communication

VerifiedSafe

Ultra-compressed communication mode. Required for summarizing artifacts, commits, PR descriptions, and status updates.

Sby Skills Guide Bot
ProductivityBeginner
207/25/2026
Claude CodeCursorWindsurfCopilotCodex
#terse-communication#ultra-compressed#commit-messages#pull-request-descriptions#code-summaries

Recommended for

Our review

Compresses communication messages (summaries, commits, PRs) to ultra-terse fragments by dropping articles and filler words.

Strengths

  • Reduces noise and gets straight to the point
  • Enables very fast communication
  • Maintains technical accuracy

Limitations

  • Can come across as rude in collaborative settings
  • Unsuitable for detailed explanations or non-technical discussions
When to use it

When writing code summaries, commit messages, or pull request descriptions to save time and focus on essentials.

When not to use it

For nuanced communication, important code comments, or security warnings that require full sentences.

Security analysis

Safe
Quality score85/100

The skill only modifies the agent's communication style for summaries, commits, and status updates, and explicitly forbids applying its rules to code, commands, or security warnings. No tools are used, and no destructive actions are instructed.

No concerns found

Examples

Commit message
Write a git commit message for the changes in the current branch using caveman style.
PR summary
Summarize this pull request in caveman mode.
Status update
Give me a status update on the project, caveman style.

name: caveman description: Ultra-compressed communication mode. The agent MUST use this skill whenever summarizing an artifact, writing a commit message, writing a PR description, or providing status updates.

Caveman Output Skill

When summarizing your work, communicating status, or writing commits, you must use terse, ultra-compressed language.

Strict Boundaries (Safety Lock)

  • Do NOT apply caveman rules to the actual codebase, file modifications, JSON outputs, or CLI commands.
  • Code generation must remain 100% syntactically correct and standard.
  • Suspend this mode and speak normally for security warnings or destructive actions (like dropping a table).

Core Rules

  1. Drop: Articles (a/an/the), filler words (just/really/basically), pleasantries, and hedging.
  2. Grammar: Sentence fragments are mandatory. Use short synonyms.
  3. Accuracy: Technical terms must remain exact.

Intensity Level

Unless instructed otherwise, use the "Full" level:

  • Drop articles. Fragments required. Short synonyms. Classic caveman.
  • Example: "Backend containerized. Dockerfile isolates Node env. docker-compose links MongoDB."
Related skills