CtrlK
BlogDocsLog inGet started
Tessl Logo

caveman-stats

Show real token usage and estimated savings for the current session. Reads directly from the Claude Code session log — no AI estimation. Triggers on /caveman-stats. Output is injected by the mode-tracker hook; the model itself does not compute the numbers.

69

Quality

83%

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

The canonical home for this skill is caveman-stats in JuliusBrussee/caveman

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is efficient and well-organized for a simple hook-driven skill, with a clear single action and appropriately shallow references. The only minor room for improvement is trimming the internal-mechanism detail and slightly sharpening output-framing guidance.

DimensionReasoningScore

Conciseness

Lean body that assumes competence and avoids explaining basics; the one mild over-explanation is the internal hook mechanism ('decision: "block"'), which could be trimmed slightly.

4 / 5

Actionability

Concrete guidance for a hook-driven skill: it tells the model it does nothing while the hook injects stats, and specifies output fields plus the CAVEMAN_RULE_OVERHEAD_TOKENS override and net-negative behavior; minor gaps in how the model should frame the output.

4 / 5

Workflow Clarity

Single-action skill whose action ('the model does not need to do anything when this skill fires') is unambiguous, and the operation is read-only/non-destructive so no validation checkpoint is needed; the simple-skill exception applies.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files; references to docs/HONEST-NUMBERS.md and the hook scripts are one level deep and clearly signaled, and the two-paragraph structure is well organized.

5 / 5

Total

18

/

20

Passed

Description

82%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.

The description is well-structured with an explicit trigger and clear what/when coverage, occupying a distinct niche. It is held back only by modest breadth of stated actions, which fits a single-purpose skill.

DimensionReasoningScore

Specificity

Names the domain and a couple concrete actions ('Show real token usage and estimated savings', 'Reads directly from the Claude Code session log'), but coverage is narrow and the skill is single-purpose, so it stops short of listing multiple specific actions.

3 / 5

Completeness

Explicitly answers both 'what' (show real token usage and estimated savings) and 'when' ('Triggers on /caveman-stats') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes the natural trigger '/caveman-stats' plus relevant phrases like 'token usage' and 'estimated savings'; a few common variations are absent but coverage is good.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (session token stats via a specific mode-tracker hook) with a distinct slash-command trigger and minimal overlap with other skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JuliusBrussee/caveman
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.