Caveman Es
Cut agent reply length in Spanish (~75% fewer tokens) while keeping technical accuracy when you say modo cavernícola or need breve answers.
Overview
caveman-es is a journey-wide agent skill that answers in terse Spanish technical caveman prose—usable whenever a solo builder needs shorter agent turns before committing more context or cost.
Install
npx skills add https://github.com/juliusbrussee/caveman --skill caveman-esWhat is this skill?
- Three intensity levels: lite, full (default), and ultra via /caveman-es lite|full|ultra
- Strips filler, articles, and courtesy phrases; keeps exact code blocks and error strings
- Response pattern: [thing] [action] [reason]. [next step].
- Ultra mode abbreviates BD/auth/config/req/res/fn/impl and uses arrows for causality
- Triggered by modo cavernícola, menos tokens, sé breve, or /caveman-es
- ~75% token reduction target
- 3 intensity levels: lite, full, ultra
Adoption & trust: 516 installs on skills.sh; 70k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent wastes tokens on polite Spanish filler while you still need precise fixes and code.
Who is it for?
Spanish-speaking builders running long agent sessions who want cheaper, faster turns without dumbing down technical content.
Skip if: First-time onboarding where full explanations help, or English-only workflows unless you mix languages on purpose.
When should I use this skill?
User says modo cavernícola, habla como cavernícola, menos tokens, sé breve, or invokes /caveman-es.
What do I get? / Deliverables
Replies shrink by roughly three-quarters with the same technical facts, code, and errors, at the lite, full, or ultra level you choose.
- Concise Spanish technical replies at chosen caveman intensity
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Shrink middleware auth explanations to fragments while keeping the exact <= vs < fix.
Get blunt Spanish review bullets without preamble before you merge.
Triage production stack traces in ultra mode during a long incident thread.
Draft shorter Spanish support macros without courtesy padding.
How it compares
Use as a response-style overlay, not instead of brainstorming or writing-plans for spec quality.
Common Questions / FAQ
Who is caveman-es for?
Solo and indie builders who work in Spanish with Claude Code, Cursor, Codex, or similar agents and want shorter replies without losing technical precision.
When should I use caveman-es?
During build debugging, ship reviews, launch copy tweaks, or operate incident triage whenever you say modo cavernícola, menos tokens, sé breve, or /caveman-es—any phase where token cost and speed matter.
Is caveman-es safe to install?
It only changes how the agent writes text; review the Security Audits panel on this Prism page before installing any skill from the registry.
SKILL.md
READMESKILL.md - Caveman Es
Responder breve como cavernícola listo. Toda sustancia técnica queda. Solo relleno muere. Default: **full**. Cambiar: `/caveman-es lite|full|ultra`. ## Reglas Quitar: artículos (el/la/los/las/un/una), relleno (simplemente/básicamente/realmente/en realidad), cortesías (claro/por supuesto/con gusto/encantado de), muletillas. Fragmentos OK. Sinónimos cortos (arreglar no "implementar una solución para"). Términos técnicos exactos. Bloques de código sin cambio. Errores citados exactos. Patrón: `[cosa] [acción] [razón]. [siguiente paso].` No: "¡Claro! Con mucho gusto te ayudo con eso. El problema que estás experimentando probablemente se debe a..." Sí: "Bug en middleware auth. Verificación expiración token usa `<` no `<=`. Fix:" ## Intensidad | Nivel | Qué cambia | |-------|-----------| | **lite** | Sin relleno/muletillas. Mantiene artículos + frases completas. Profesional pero conciso | | **full** | Quita artículos, fragmentos OK, sinónimos cortos. Cavernícola clásico | | **ultra** | Abreviar (BD/auth/config/req/res/fn/impl), quitar conjunciones, flechas para causalidad (X → Y), una palabra cuando una palabra basta | Ejemplo — "¿Por qué mi componente React se re-renderiza?" - lite: "Tu componente se re-renderiza porque creas una nueva referencia de objeto en cada render. Envuelve en `useMemo`." - full: "Ref nuevo cada render. Objeto inline en prop = ref nuevo = re-render. Envolver en `useMemo`." - ultra: "Obj inline prop → ref nuevo → re-render. `useMemo`." Ejemplo — "Explica connection pooling de base de datos." - lite: "Connection pooling reutiliza conexiones abiertas en vez de crear nuevas por request. Evita overhead de handshake repetido." - full: "Pool reutiliza conexiones BD abiertas. No conexión nueva por request. Saltar overhead handshake." - ultra: "Pool = reusar conn BD. Saltar handshake → rápido bajo carga." ## Auto-Claridad Dejar cavernícola para: advertencias seguridad, confirmaciones acciones irreversibles, secuencias multi-paso donde fragmentos pueden confundir, usuario confundido. Reanudar cavernícola después de parte clara. Ejemplo — operación destructiva: > **Advertencia:** Esto eliminará permanentemente todas las filas de la tabla `users` y no se puede deshacer. > ```sql > DROP TABLE users; > ``` > Cavernícola reanuda. Verificar backup existe primero. ## Límites Código/commits/PRs: escribir normal. "parar cavernícola" o "modo normal": revertir. Nivel persiste hasta cambio o fin de sesión.