CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

progress-tracker

Track and report progress across autonomous coding sessions. Use when generating progress reports, calculating metrics, visualizing completion, or estimating time to completion.

Quality

80%

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 ./.claude/skills/progress-tracker/SKILL.md

The canonical home for this skill is progress-tracker in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A concise, actionable body whose quick start makes the skill immediately usable. The standout defect is a dangling reference: REPORT-FORMATS.md is promised in the References section but absent from the bundle, and the ASCII dashboard and metrics table add mild padding.

Suggestions

Create the missing references/REPORT-FORMATS.md file (or remove the References entry pointing to it), since half of the body's reference links currently lead nowhere.

Trim or shorten the 26-line ASCII dashboard example — the visualize_progress quick-start snippet already demonstrates the output format.

Clarify how 'project_dir' is obtained and how the scripts/ package is imported (e.g., sys.path setup or a documented path convention) so the quick-start code is truly copy-paste executable.

DimensionReasoningScore

Conciseness

The quick start is lean and free of concept explanations Claude already knows, but the 26-line ASCII dashboard example and the metrics table largely duplicate information already conveyed by the code examples and could be trimmed.

4 / 5

Actionability

Concrete, near-copy-paste code covers the common cases (get_progress, generate_report, visualize_progress), with minor gaps: 'project_dir' is never defined and there is no note on how the 'scripts.progress_tracker' import path is resolved.

4 / 5

Workflow Clarity

As a simple single-purpose API skill, the quick start's usage sequence is unambiguous and no validation checkpoints are needed since operations are read-only. It falls short of 5 because it never explains how to obtain 'project_dir' or how the listed integration points (e.g., autonomous-loop continuation decisions) actually consume the metrics.

4 / 5

Progressive Disclosure

Structure is good — quick start inline, one-level-deep references and scripts clearly signaled — but the body cites 'references/REPORT-FORMATS.md - Report format options' and that file does not exist in the bundle (only references/METRICS.md is present), so a signaled navigation target dangles and the report-format content is effectively missing.

3 / 5

Total

15

/

20

Passed

Description

83%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.

A well-constructed description with an explicit 'Use when...' clause covering four concrete triggers and a clearly stated purpose. Its main weakness is the slightly generic opening verb phrase and a few missing natural synonyms users might use.

DimensionReasoningScore

Specificity

The description lists several specific actions — 'generating progress reports, calculating metrics, visualizing completion, or estimating time to completion' — but opens with the generic 'Track and report progress', leaving minor gaps in coverage rather than the comprehensive concrete-action list of the top anchor.

4 / 5

Completeness

It clearly answers both questions: 'Track and report progress across autonomous coding sessions' states what it does, and an explicit 'Use when generating progress reports, calculating metrics, visualizing completion, or estimating time to completion' gives four concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases like 'progress reports', 'metrics', and 'estimating time to completion' match what users would say, but common synonyms such as 'ETA', 'status report', or 'percentage complete' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'autonomous coding sessions' scope carves a clear niche that would not fire for unrelated skills, though it could still overlap with generic status-report or metrics skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/progress-tracker/SKILL.md

Revision

93ed392

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill