CtrlK
BlogDocsLog inGet started
Tessl Logo

insights

Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Computes stats from project memory and session history. Use when asking for stats, statistics, progress, how am I doing, coding history, or dashboard.

79

1.02x
Quality

68%

Does it follow best practices?

Impact

99%

1.02x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/insights/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

37%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides a clear vision of what analytics output should look like with well-formatted example blocks, and the data source commands are concrete. However, it critically lacks the computational logic to transform raw data into the displayed metrics—there's no code for counting corrections, computing rates, categorizing learnings, or generating heatmaps. The workflow is essentially 'gather data → [magic] → show report' with the middle step entirely missing.

Suggestions

Add executable code or detailed algorithmic steps for computing each metric (correction rate, category breakdown, stale learning detection) from the raw data sources.

Define a clear sequential workflow: 1) gather data, 2) parse/categorize, 3) compute metrics, 4) validate completeness, 5) format output—with handling for missing or incomplete data.

Specify how to identify 'corrections' programmatically—the current definition ('any instance where the user redirected, fixed, or overrode agent output') is too vague to implement without concrete parsing logic.

Consolidate the four output example blocks into a single representative example or move detailed format specifications to a separate reference file.

DimensionReasoningScore

Conciseness

The skill is moderately efficient but includes some redundancy—the 'What It Shows' section with four large example blocks is verbose, and the 'Output' section at the end largely restates what was already shown. Some trimming would help, though it doesn't over-explain concepts Claude already knows.

2 / 3

Actionability

The data gathering commands are concrete and executable, but the actual computation of metrics (correction rate, heatmap generation, session duration, stale learning detection) is entirely unspecified. The skill shows desired output formats but provides no code or logic for how to derive those numbers from the raw data sources.

2 / 3

Workflow Clarity

There is no clear sequenced workflow—the skill lists data sources and shows desired outputs but never specifies the steps to go from raw data to computed analytics. There are no validation checkpoints, no error handling for missing data, and no feedback loops for when data sources are incomplete or unavailable.

1 / 3

Progressive Disclosure

The content is organized into logical sections with clear headers, which is good. However, the four large output example blocks make the file quite long and could be split into a reference file. No bundle files are provided, so there's no progressive disclosure to external references, though for a skill of this complexity some separation would be beneficial.

2 / 3

Total

7

/

12

Passed

Description

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 well-crafted skill description that clearly communicates what the skill does, how it works, and when it should be triggered. It lists specific concrete outputs, explains the data source, and provides a comprehensive set of natural trigger terms covering both formal and colloquial user phrasings. It follows the third-person voice convention and is concise without being vague.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'session analytics, learning patterns, correction trends, heatmaps, and productivity metrics' along with the method 'Computes stats from project memory and session history.'

3 / 3

Completeness

Clearly answers both 'what' (show session analytics, learning patterns, correction trends, heatmaps, productivity metrics; computes stats from project memory and session history) and 'when' (explicit 'Use when' clause with multiple trigger phrases).

3 / 3

Trigger Term Quality

Includes a strong set of natural keywords users would actually say: 'stats', 'statistics', 'progress', 'how am I doing', 'coding history', 'dashboard'. These cover both formal and casual phrasings.

3 / 3

Distinctiveness Conflict Risk

The combination of session analytics, learning patterns, correction trends, heatmaps, and productivity metrics creates a clear niche. The trigger terms like 'dashboard', 'how am I doing', and 'coding history' are distinctive and unlikely to conflict with other skills.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/pro-workflow
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.