CtrlK
BlogDocsLog inGet started
Tessl Logo

progressive-estimation

Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops

36

Quality

34%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/progressive-estimation/SKILL.md

The canonical home for this skill is progressive-estimation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

28%Scale 1-5

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

This skill reads like a marketing overview or README rather than an actionable skill file. It describes what Progressive Estimation does at a conceptual level but provides zero concrete implementation: no formulas, no multiplier values, no classification criteria, no PERT calculation examples, and no executable code or commands. Claude would not be able to perform estimation from this content alone.

Suggestions

Add the actual PERT formula (E = (O + 4M + P) / 6) with concrete examples showing input values and calculated output for at least one task size

Include the specific multipliers for human-only, hybrid, and agent-first modes with a lookup table or decision tree

Provide the task classification criteria (what makes something XS vs XL) with concrete examples rather than just listing the labels

Add at least one complete worked example showing a task going through all 7 steps with actual numbers, producing a final estimate with confidence bands

DimensionReasoningScore

Conciseness

The content is moderately efficient but includes some unnecessary sections like 'Overview' that restates the title/description, and 'When to Use This Skill' which lists fairly obvious use cases Claude could infer. The 'How It Works' section describes a process at a high level without adding actionable detail.

3 / 5

Actionability

The skill provides no concrete code, commands, formulas, or executable guidance. It describes what the skill does conceptually ('applies research-backed multipliers,' 'PERT calculation') but never shows the actual formulas, multipliers, classification criteria, or any concrete implementation. The examples show prompts to give, not how to perform the estimation.

1 / 5

Workflow Clarity

The 'How It Works' section lists 7 steps at a very high level but provides no specifics on how to execute any of them — no formulas for PERT calculation, no multiplier values, no classification criteria, no validation checkpoints. The steps are essentially labels without substance.

2 / 5

Progressive Disclosure

The skill references external resources (GitHub repo, installation guide, research references) and related skills, which is good structure. However, there are no bundle files provided, so the references to formulas, multipliers, and calibration systems that should be in supporting files are simply missing rather than properly disclosed. The content that should be the core of the skill (formulas, multipliers, classification criteria) is neither inline nor referenced.

3 / 5

Total

9

/

20

Passed

Description

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

The description identifies a specific niche (AI-assisted development estimation using PERT) but relies heavily on jargon without explaining concrete actions or providing trigger guidance. It lacks a 'Use when...' clause, which is critical for skill selection, and the buzzword-heavy phrasing ('research-backed', 'calibration feedback loops') adds little clarity about what the skill actually does.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases like 'estimate how long a task will take', 'project planning', 'effort estimation', or 'time estimate for development work'.

Replace abstract phrases like 'calibration feedback loops' with concrete actions such as 'generates three-point estimates, calculates expected duration and confidence intervals, tracks estimation accuracy over time'.

Include natural synonyms and user-facing terms like 'time estimation', 'project timeline', 'how long will this take', 'sprint planning' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (AI-assisted development estimation) but the actions are vague. 'Estimate' is one concrete verb, but 'research-backed PERT statistics' and 'calibration feedback loops' are buzzword-heavy without explaining what concrete actions the skill performs (e.g., generate estimates, produce confidence intervals, track actuals vs predictions).

2 / 5

Completeness

Provides a vague 'what' (estimate development work with PERT and calibration) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which per the rubric caps completeness at 3, and the 'what' itself is not clearly articulated enough to reach 3.

2 / 5

Trigger Term Quality

Contains some relevant keywords like 'estimate', 'PERT', 'development work', and 'human+agent', but misses natural user phrases like 'how long will this take', 'project planning', 'time estimate', 'effort estimation', 'story points', or 'sprint planning'. Users seeking estimation help may not use terms like 'calibration feedback loops'.

3 / 5

Distinctiveness Conflict Risk

The combination of AI-assisted development estimation, PERT statistics, and calibration feedback loops is fairly niche and unlikely to conflict with most other skills. Minor overlap risk exists with general project management or estimation skills, but the specific methodology (PERT) and focus on hybrid human+agent work provides reasonable distinctiveness.

4 / 5

Total

11

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.