insights
Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Use when wanting to understand your coding patterns over time.
80
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
77%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 solid description that clearly lists specific capabilities and includes an explicit 'Use when' clause. The main weaknesses are limited trigger term coverage (missing common synonyms users might say) and moderate overlap risk with other analytics or productivity-focused skills.
Suggestions
Add more natural trigger terms users might say, such as 'stats', 'statistics', 'progress', 'how am I doing', 'coding history', or 'dashboard'
Strengthen distinctiveness by emphasizing the coding/development context more explicitly in the trigger clause, e.g., 'Use when wanting to see coding statistics, development progress, or understand programming patterns over time'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'session analytics, learning patterns, correction trends, heatmaps, and productivity metrics' - these are distinct, measurable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics') and when ('Use when wanting to understand your coding patterns over time'). | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'analytics', 'patterns', 'metrics', but missing common variations users might say like 'stats', 'statistics', 'progress', 'history', or 'dashboard'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to coding analytics, but 'productivity metrics' and 'learning patterns' could overlap with general productivity or learning management skills. The coding focus helps but isn't strongly emphasized in triggers. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at defining clear, well-formatted output examples and is appropriately concise. However, it functions more as a specification of what to display rather than actionable guidance on how to retrieve or compute the analytics data. The skill would benefit from concrete instructions on accessing session history and project memory.
Suggestions
Add concrete guidance on how to access/query session history and project memory to compute these metrics
Include example code or commands for retrieving the underlying data (e.g., file paths, data structures, or API calls)
Specify what constitutes a 'correction' and how to detect/count them programmatically
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using formatted examples to show exactly what output looks like without explaining concepts Claude already knows. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | The skill shows clear output formats and examples, but lacks executable code or commands for how to actually generate these analytics. It describes what to show rather than how to compute or retrieve the data. | 2 / 3 |
Workflow Clarity | This is primarily a display/reporting skill with no multi-step process, but the guardrails mention using 'actual data from project memory and session history' without explaining how to access or query this data. The workflow for generating insights is implicit. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines focused on a single task (displaying analytics), the content is well-organized with clear sections for different types of insights. No external references needed for this scope. | 3 / 3 |
Total | 10 / 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.