stats
Show ToonDex debug mode usage statistics. Tracks hook fires, index.toon reads, and effectiveness metrics.
76
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 identifies a specific domain (ToonDex debug mode) with reasonable technical specificity, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and relies on technical jargon that users may not naturally use when requesting this functionality.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about ToonDex performance, debugging, or wants to see usage statistics.'
Include more natural language variations users might say, such as 'stats', 'how often', 'performance metrics', or 'debug info'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ToonDex debug mode) and some actions (tracks hook fires, index.toon reads, effectiveness metrics), but doesn't comprehensively list what specific statistics are shown or what actions can be taken with them. | 2 / 3 |
Completeness | Describes what it does (shows debug statistics, tracks metrics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'debug mode', 'statistics', 'hook fires', 'index.toon', but these are fairly technical. Missing common variations users might say like 'stats', 'metrics', 'debugging', or 'usage data'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to 'ToonDex debug mode' which is a clear niche. The combination of ToonDex, hook fires, and index.toon creates distinct triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary simple skill that executes a single task with maximum efficiency. It provides exact commands, handles edge cases (script path fallback, debug mode disabled), and respects Claude's intelligence by not over-explaining. The directive to execute immediately rather than explain is appropriate for a stats display command.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows how to run bash commands, every line serves a purpose. | 3 / 3 |
Actionability | Provides exact executable commands with environment variables, a fallback path, and specific user guidance. Copy-paste ready with no ambiguity. | 3 / 3 |
Workflow Clarity | For this simple single-task skill, the workflow is unambiguous: run command, show output, handle the debug-not-enabled case. Clear sequence with appropriate conditional handling. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single purpose, the content is well-organized with clear sections (Execute Now, fallback, debug mode guidance). No external references needed. | 3 / 3 |
Total | 12 / 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.
- 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.