Caveman

What it does

Caveman is a persistent communication-style skill within a larger project that also contains compression and workflow tools. The selected file changes how responses are written; it is not itself a model, code optimizer or guarantee of lower total API spend. Its core requirement is that removing filler must preserve information the reader needs.

When to use it

• Terminal-based development updates contain too much repeated explanation.
• An experienced team wants direct findings and exact commands.
• A long debugging conversation needs compact progress messages.

Step-by-step workflow

1. Activate the communication style in a supporting client.
2. Put the result or required action first.
3. Remove repeated framing while retaining technical facts and conditions.
4. Keep code, paths, commands and error strings exact; use fuller language when compression creates ambiguity.
5. Check that the reader can still reproduce the action; explicitly turn the mode off when normal prose is wanted.

Example request

Use caveman for development updates in this session. State the finding, affected file and next action briefly. Preserve commands and errors exactly. Keep normal explanatory sentences for security issues, destructive actions and any procedure that would become ambiguous when shortened.

Worked example

A useful compact test report names the failing check and its reason. Dropping the environment or prerequisite may make it shorter but unusable. Judge the result by whether a teammate can act on it, not by the fewest characters.

What you get

Shorter conversational output with the same actionable technical content.

How to evaluate the result

• Confirm the requested artifact or behavior is actually delivered, with evidence appropriate to this workflow.
• Repeat the example on your own inputs and check the stated limits; repository popularity is not an execution test.
• Verify important facts, permissions and failure paths before adopting the result.

What you need

A skills-capable agent and a clear preference for compact communication.

Setup and activation

Follow the publisher README for your specific client and preserve the complete selected skill folder, including companion references and scripts. Claude Code, Codex and other hosts may use different plugin or Agent Skills installation paths. This guide does not establish that every host has the same tools. Security-scan the exact version before installation; this website installs or executes nothing.

Limits and considerations

The source distinguishes this voice from other modes and tools in the repository. Publisher token-saving claims are not measurements of your workload. Persistent style can be inappropriate for teaching or complex instructions.

Related workflows

• Use a task-specific validation workflow to check the final result.
• Review companion scripts and references before adding this skill to an agent.

License and reuse

Apache-2.0 at repository level; inspect per-file terms and separately licensed assets before reuse.

Further reading

• Publisher setup and compatibility instructions
• Reviewed skill version (immutable commit)