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.
56
63%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/caveman/skills/caveman-stats/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that clearly communicates what the skill does (show token usage and savings from session logs), when it triggers (on /caveman-stats), and how it works (injected by mode-tracker hook, not AI-computed). The explicit trigger command and specific domain make it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Show real token usage and estimated savings', 'Reads directly from the Claude Code session log', 'Output is injected by the mode-tracker hook'. Also clarifies what the model does NOT do ('no AI estimation', 'the model itself does not compute the numbers'). | 3 / 3 |
Completeness | Clearly answers 'what' (show real token usage and estimated savings by reading session logs) and 'when' (triggers on /caveman-stats). The explicit trigger clause satisfies the 'Use when' requirement. | 3 / 3 |
Trigger Term Quality | Includes the explicit trigger '/caveman-stats' and natural terms like 'token usage', 'estimated savings', 'session', 'session log'. These are terms a user would naturally associate with checking usage statistics. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a unique slash command trigger '/caveman-stats', specific to Claude Code session logs, and clearly scoped to token usage/savings tracking. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a brief explanation that the model should do nothing — the hook handles everything. While brevity is valued, the content provides no actionable information: no example output, no fallback behavior, no verification that the hook is working, and no bundle files to support the referenced paths. It reads more like a comment than a skill.
Suggestions
Add an example of the stats output so Claude (or a developer) knows what to expect when /caveman-stats fires.
Include the referenced hook files (hooks/caveman-stats.js, hooks/caveman-mode-tracker.js) in the bundle, or inline the key logic so the skill is self-contained.
Add a brief fallback instruction for what Claude should do if the hook is not installed or fails to respond (e.g., inform the user the hook is missing).
If the model truly does nothing, consider whether this needs to be a SKILL.md at all, or if a one-line note in a parent skill would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief (3 sentences), but it spends tokens explaining what the model doesn't need to do and how the hook works internally — information Claude doesn't need if it truly does nothing. Could be reduced to a single sentence. | 2 / 3 |
Actionability | There is no actionable guidance whatsoever — no code, no commands, no examples of output. The skill explicitly says the model does nothing, yet provides no reference to the hook implementation, no example of what the stats output looks like, and no fallback instructions. | 1 / 3 |
Workflow Clarity | The workflow is implicitly simple (user types /caveman-stats, hook responds), but there's no explicit description of the trigger-response flow, no mention of what happens if the hook isn't installed or fails, and no example output. | 2 / 3 |
Progressive Disclosure | References `hooks/caveman-stats.js` and `hooks/caveman-mode-tracker.js` but no bundle files are provided, so these references are unverifiable. There's no structured navigation, no sections, and no links to supporting documentation. | 1 / 3 |
Total | 6 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
655b7d9
Table of Contents
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.