CtrlK
BlogDocsLog inGet started
Tessl Logo

caveman-stats

Show real token usage and estimated savings for the current session, read from the session log. Trigger: /caveman-stats.

63

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/caveman-stats/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 efficiently documents a hook-delivered, model-no-op skill with a clear single action and one well-signaled external reference. Actionability is inherently limited because the model takes no action, and the absence of section structure keeps progressive disclosure just below the top anchor.

Suggestions

Add brief section headers (e.g. "## What this skill does" and "## Output fields") to lift progressive_disclosure from 4 to 5.

Surface the rule-overhead/net output behavior in the description so specificity reflects the skill's full feature set.

Include a few natural user-side trigger phrases (e.g. "token cost", "tokens used", "session spend") alongside the slash command to broaden trigger-term coverage.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence (hook filenames, env var, default token value stated directly), with only minor editorial padding such as "rather than hiding the net-negative regime behind a gross-savings number", fitting the efficient level-4 anchor over the more padded level-3.

4 / 5

Actionability

Concrete specifics exist (the CAVEMAN_RULE_OVERHEAD_TOKENS override, the 1,250 tokens/turn default, named output lines, referenced hook files), but because "The model does not need to do anything when this skill fires," the guidance is largely explanatory rather than executable, sitting at level 3 rather than the mostly-executable level 4.

3 / 5

Workflow Clarity

This is a simple single-action skill whose one action is stated unambiguously ("the hook returns decision: block with the formatted stats as the reason. The user sees the numbers immediately"), qualifying for the simple-skill exception; it is not a destructive/batch operation so the level-3 validation cap does not apply.

5 / 5

Progressive Disclosure

The short body is a concise overview with one clearly signaled one-level reference ("(see docs/HONEST-NUMBERS.md)"), but it lacks section headers (just two prose paragraphs), so it lands at the well-structured level 4 rather than the cleanly sectioned level 5.

4 / 5

Total

16

/

20

Passed

Description

75%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 concise, third-person, and explicitly covers both what the skill does and when it fires via a concrete trigger, with low conflict risk. Its main weakness is trigger-term breadth and action specificity, which stay at the mid-level anchors.

DimensionReasoningScore

Specificity

"Show real token usage and estimated savings" and "read from the session log" name the domain plus 1-2 concrete actions, but coverage is not comprehensive (rule overhead/net lines are absent from the description), matching the level-3 anchor rather than the broader level-4.

3 / 5

Completeness

It states clearly what it does ("Show real token usage and estimated savings for the current session") and gives equivalent explicit trigger guidance ("Trigger: /caveman-stats"), so it satisfies both the what and the when with a concrete trigger phrase; it is not capped at 3 because explicit trigger guidance is present.

5 / 5

Trigger Term Quality

The explicit "Trigger: /caveman-stats" plus "token usage"/"estimated savings"/"session log" give some relevant keywords, but natural synonyms and variations a user might say (e.g. "cost", "spend", "tokens used") are missing, fitting level 3 rather than the well-covered level 4.

3 / 5

Distinctiveness Conflict Risk

The narrow caveman-stats niche and a distinct slash-command trigger (/caveman-stats) make conflict with other skills unlikely, matching the level-5 "clear niche with distinct triggers; minimal conflict risk" anchor.

5 / 5

Total

16

/

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.