CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ultracave

Caveman at maximum compression: fragments, one word when one word is enough, each fact once. Invoke only with /ultracave or /caveman ultra. Stays on until "stop caveman" or "normal mode".

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary instruction-only skill body: lean to the point of demonstrating its own compression style, with concrete Bad/Good examples for the ambiguous cases, an explicit floor of protected content, and a pre-send validation checklist. The only nitpick is the undefined `/caveman-compress` exemption mention, which is peripheral.

DimensionReasoningScore

Conciseness

The body practices what it preaches: "Respond terse like smart caveman. All technical substance stay. Only fluff die." No concept Claude already knows is explained, every rule is stated once, and examples are minimal Bad/Good pairs. Every token earns its place.

5 / 5

Actionability

For an instruction-only skill, guidance is fully executable: concrete Bad/Good pairs ("Bad: 'The component re-renders because an inline object prop creates a new reference each render.' Good: 'Inline object prop, new ref, re-render. `useMemo`."), an explicit protected-content list ("Never cut: code, commands, paths, API names, error strings (verbatim)..."), and a precise `/caveman status` fallback ("relay the hook's `Caveman mode: <mode>` value; with no hook, the mode you were in (or `off`) plus `(not tracked by this host)`"). The example pairs cover the common compression cases.

5 / 5

Workflow Clarity

A single-action skill (respond in compressed fragments) whose action is unambiguous, satisfying the simple-skill exception. The "Pre-send check" section provides an explicit validation checkpoint before every response ("Two readings? Full sentence. Negations present? Payload verbatim? Flavor word? Cut."), and no destructive or batch operations exist that would cap the score.

5 / 5

Progressive Disclosure

Self-contained single-purpose skill with well-organized sections (Persistence, Floor, Rules, When to break the rules, Pre-send check) and no bundle files or external references needed — nothing here would benefit from being split out. Structure is clear and easy to navigate.

5 / 5

Total

20

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, trigger-explicit description that states what the skill does, exactly how to invoke and dismiss it, and how it differs from a sibling caveman skill. It is written in the skill's own compressed style, which fits its purpose. Coverage of capabilities and natural-language synonyms is slightly incomplete, but nothing is vague or padded.

DimensionReasoningScore

Specificity

Lists several concrete behaviors — "fragments, one word when one word is enough, each fact once" plus persistence behavior ("Stays on until 'stop caveman' or 'normal mode'") — but omits other capabilities from the body (protected content, break-the-rules cases), so coverage has minor gaps. Not 3 because it goes beyond 1-2 actions; not 5 because the capability list is not comprehensive.

4 / 5

Completeness

Explicitly answers both: what ("Caveman at maximum compression: fragments, one word when one word is enough, each fact once") and when ("Invoke only with /ultracave or /caveman ultra"). The 'when' uses concrete trigger phrases and even states the mode's lifetime, matching the anchor for a fully explicit what+when pair.

5 / 5

Trigger Term Quality

Gives the exact natural invocation phrases users would type for this command-only skill — "/ultracave", "/caveman ultra", "stop caveman", "normal mode" — covering both entry and exit. Not 5 because natural-language synonyms a user might say ("terse", "brief", "compress responses") are absent, which would matter if it were model-invoked.

4 / 5

Distinctiveness Conflict Risk

"Caveman at maximum compression" carves a clear niche distinct from a base caveman skill, and invocation is restricted to exact slash commands ("Invoke only with /ultracave or /caveman ultra"), so the risk of triggering the wrong skill is minimal. Third-person voice is used throughout, per the guideline.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

JuliusBrussee/caveman

Path

skills/ultracave/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.