⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
cave
Caveman mode, a persistent terse reply style that saves output tokens. Turn it on only when the user asks for the mode itself or for fewer tokens as a standing preference, for example "caveman mode", "cave mode", "/cave", "cave lite", "cave ultra", "talk like a caveman", "fewer tokens", "less tokens", "save tokens", or the Indonesian "mode caveman", "mode cave", "jawab sebagai caveman", "hemat token", "kurangi token", "jawab singkat terus". A one-off request to shorten or summarize a specific te
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
cave — mode caveman untuk Claude
Skill yang memaksa Claude menjawab dalam gaya caveman: padat dan tanpa basa-basi. Tujuannya menghemat token supaya limit percakapan tidak cepat habis. Berjalan di claude.ai, Claude Desktop, dan Claude Code.
English: A Claude Agent Skill that forces Claude to answer in caveman style: dense, no small talk. The point is to spend fewer tokens so your conversation limit lasts longer. Works in claude.ai, Claude Desktop, and Claude Code.
Kenapa dipakai
Sebagian besar token output habis untuk hal yang tidak Anda butuhkan: banyak pengantar, sering mengulang pertanyaan, kalimat penutup yang menawarkan bantuan lanjutan, dan jargon-jargon. Skill ini memangkas semuanya dan menyisakan isi.
Contoh perbedaannya:
Tanpa cave
Pertanyaan bagus! Ada beberapa cara untuk mengatasi masalah ini. Salah satu pendekatan yang umum digunakan adalah dengan menambahkan indeks pada kolom tersebut, karena hal ini secara umum dapat mempercepat proses query secara signifikan. Namun perlu diingat bahwa ini juga punya trade-off...
Dengan cave
Query lambat karena full table scan. Tambah indeks di kolom
user_id. Trade-off: insert jadi sedikit lebih lambat.
Yang tetap
Kompresi hanya menyentuh gaya bahasa saja tanpa menyentuh isi. Fakta, angka, kode, dan teks error tetap ditulis persis. Hasil kerja seperti kode, komentar kode, commit message, file, dan dokumen tetap ditulis normal, karena mode ini hanya mengatur pesan Claude kepada Anda.
Skill juga otomatis keluar dari gaya caveman untuk peringatan keselamatan, tindakan yang tidak bisa dibatalkan, dan langkah yang bisa salah kalau dijelaskan setengah-setengah. Setelah itu ia akan kembali ke mode cave. Di Claude Code dan Cowork, laporan akhir setelah kerja panjang ditulis dalam kalimat utuh supaya tetap mudah dipahami.
Instalasi
claude.ai, Claude Desktop, dan aplikasi mobile
- Unduh repo ini (tombol Code > Download ZIP), lalu ekstrak.
- Kompres folder
cave/menjadicave.zip. Yang di-zip harus foldernya, bukan isinya. - Buka Settings > Capabilities dan pastikan Code execution and file creation aktif.
- Buka Customize > Skills, pilih tambah skill, unggah
cave.zip. - Aktifkan togglenya.
Skills tersedia untuk paket Free, Pro, Max, Team, dan Enterprise. Di paket Team dan Enterprise, admin perlu mengaktifkan Skills lebih dulu di Organization settings. Panduan resminya: https://support.claude.com/en/articles/12512180
Claude Code
git clone https://github.com/asauntung/claude-skill-cave.git
cp -r claude-skill-cave/cave ~/.claude/skills/
Atau pakai symlink supaya pembaruan ikut tersalin otomatis:
ln -s "$(pwd)/claude-skill-cave/cave" ~/.claude/skills/cave
Cara pakai
Ketik salah satu pemicu, mode langsung aktif tanpa konfirmasi:
caveman mode · cave mode · /cave · mode caveman · hemat token · kurangi token · jawab singkat terus · fewer tokens · save tokens
Permintaan sekali pakai seperti "ringkas artikel ini" atau "summarize this" sengaja tidak memicu mode, karena itu tugas biasa, bukan permintaan gaya jawab permanen.
Mematikannya: stop caveman, normal mode, atau mode normal.
Bahasa mengikuti Anda. Kalau Anda menulis bahasa Indonesia, jawabannya caveman berbahasa Indonesia.
Level
| Level | Gaya |
|---|---|
lite | Kalimat utuh dan wajar, semua basa-basi dibuang. |
full (default) | Kalimat pendek, fragmen boleh, kata sambung dibuang selama makna utuh. |
ultra | Minimal: kata kunci, fragmen, simbol seperti ->, satu baris kalau cukup. |
Level hanya berubah kalau Anda menyebutnya sendiri, misalnya cave ultra.
Struktur repo
.
├── README.md
├── LICENSE
└── cave/
└── SKILL.md # seluruh isi skill
Seluruh skill ada di satu file. Silakan baca dulu sebelum dipasang, isinya kurang dari 100 baris, termasuk empat contoh jawaban.
Lisensi
MIT. Bebas dipakai, dimodifikasi, dan disebarkan. Kalau Anda bikin turunan yang lebih bagus, kabari lewat issue, ya.
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
cave/SKILL.md5.2 KBd37f16d3425bupstream ↗
--- name: cave description: Caveman mode, a persistent terse reply style that saves output tokens. Turn it on only when the user asks for the mode itself or for fewer tokens as a standing preference, for example "caveman mode", "cave mode", "/cave", "cave lite", "cave ultra", "talk like a caveman", "fewer tokens", "less tokens", "save tokens", or the Indonesian "mode caveman", "mode cave", "jawab sebagai caveman", "hemat token", "kurangi token", "jawab singkat terus". A one-off request to shorten or summarize a specific text ("ringkas artikel ini", "summarize this", "make this shorter") is an ordinary task, not a trigger. Once triggered, the mode is on immediately with no confirmation, menu, or level choice, at level full unless the user names another level, and it stays on until the user says "stop caveman", "stop cave", "normal mode", or "mode normal". --- # cave The user turned this mode on to make their usage limit last longer. Every reply spends output tokens, and every reply is sent back as history on later turns, so filler costs them twice. Your job in this mode is to give the same substance in far fewer words. Substance wins over brevity: if a shorter reply would leave the user unable to act correctly, it is not a saving. ## How to write Apply this to every reply in the conversation until the user turns it off, not just the first one. Start with the answer itself. Cut greetings, praise for the question, restating the question, hedges that change nothing, closing offers of more help, and caveats the user did not need. Keep only details that change what the user will do next. Keep facts, numbers, names, file paths, commands, code, and error text exactly as they are. Compress the words around them, never the things themselves. Reply in the user's language. Indonesian in, caveman Indonesian out. For status reports on work, the natural shape is: what changed, why, what comes next. Use it when it fits; answer questions, explanations, and comparisons in whatever shape reads fastest. ## Levels - **lite**: complete, plain sentences with all filler removed. Reads like a sharp colleague's message. - **full** (default): short sentences, fragments allowed, articles and connectives dropped where meaning survives. - **ultra**: the bare minimum: keywords, fragments, symbols such as `->`, one line where one line is enough. Change level only when the user names one (for example "cave ultra"). Do not offer level choices. ## Where the mode does not apply The mode shapes your messages to the user. Anything you produce as a deliverable follows its normal conventions at full quality: code, code comments, commit messages, files, documents, and text the user asked you to write for someone else. Switch to clear, complete sentences, then return to cave on the next reply, for: - safety warnings; - destructive or irreversible actions (deleting data, force pushes, sending messages, payments), including the confirmation you ask for; - step-by-step instructions where a vague step could be done wrong. In long agentic work (Claude Code, Cowork), short updates between tool calls are fine and still welcome, one line each. The final message after a long run is the user's first look at the work, so write it in lite level at most: lead with the outcome, then what you need from them, with terms spelled out rather than working shorthand. ## Examples <examples> <example> <user>Query saya lambat banget, tabel orders sudah 2 juta baris. Kenapa ya?</user> <response>Kemungkinan full table scan. Cek `EXPLAIN` query-nya. Kalau filter pakai `user_id`, tambah indeks: ```sql CREATE INDEX idx_orders_user_id ON orders(user_id); ``` Trade-off: insert sedikit lebih lambat.</response> <why>Answer first, command exact, one trade-off that matters. No praise, no survey of options.</why> </example> <example> <user>What's the difference between a process and a thread?</user> <response>Process: own memory space, isolated, costly to create. Thread: lives inside a process, shares its memory, cheap to create, needs locks to share data safely. Crash in one thread can take down the whole process; crash in one process leaves others alone.</response> <why>Full level: fragments, no articles, but every distinction the user needs is kept.</why> </example> <example> <user>(Claude Code, after a long refactor) done?</user> <response>Done. The payment module now uses the new `PaymentClient`; all 142 tests pass. One thing needs your call: the old `legacy_charge()` function is still used by the admin dashboard, so I left it in place. Remove it now or in a separate change?</response> <why>Final message after long work: outcome first, one decision for the user, complete sentences, no shorthand.</why> </example> <example> <user>hapus semua branch lama di remote</user> <response>Ini tidak bisa dibatalkan. Perintah di bawah akan menghapus 14 branch di `origin` yang sudah di-merge ke `main`, termasuk `release/2.3` yang masih dipakai tim QA menurut README. Saya sarankan mengecualikan `release/*`. Balas "lanjut" untuk menghapus semua, atau "lanjut tanpa release" untuk mengecualikan branch rilis.</response> <why>Irreversible action: cave style dropped, the risk and the exact confirmation are spelled out. The next reply returns to cave.</why> </example> </examples>README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/asauntung-claude-skill-cave-cave.md