CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

progressive-estimation

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

Quality

62%

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

53%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 well-organized, readable overview that clearly frames scope, use cases, and pitfalls, but it stays entirely at the descriptive level: no formulas, multipliers, commands, or worked examples, so Claude could not actually execute an estimate from this document alone. The batch-sizing capability also lacks any validation guidance, and the real substance lives only in a remote repository rather than bundled references.

Suggestions

Add the concrete PERT formula (e.g., E = (O + 4M + P) / 6) plus one fully worked numeric example showing inputs, multipliers, and the resulting P50/P75/P90 values, so the skill instructs rather than describes.

Since batch mode handles up to 500 issues, add an explicit validation checkpoint for batch runs (e.g., cross-check aggregate estimates against historical velocity, flag outliers beyond a stated threshold).

Bundle the research references and multiplier tables as local reference files (e.g., references/formulas.md, references/multipliers.md) instead of linking only to the remote GitHub repository, which Claude cannot reliably fetch.

Remove the Overview section's verbatim restatement of the frontmatter description to reclaim redundant tokens.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no explanations of concepts Claude already knows, but the H1 intro and Overview sections both restate the frontmatter description nearly verbatim, and phrases like 'statistical estimates rather than gut feelings' and 'grounded in empirical studies' are mild padding. Anchor 4 (efficient with minor trimmable instances) fits; not 5 due to that redundancy, not 3 because there is no real over-explanation.

4 / 5

Actionability

The body describes the pipeline ('Applies research-backed multipliers', 'Produces expected values using three-point estimation', 'Generates P50, P75, P90 intervals') but never provides the PERT formula, multiplier values, commands, or a worked numeric example — the Examples section shows only input phrasings with no outputs. High-level hints with named steps and categories sit at anchor 2; not 1 because the steps, size classes (XS–XL), and output targets are concretely named, not 3 because there is no executable code or formula anywhere.

2 / 5

Workflow Clarity

The 7-step 'How It Works' sequence is clearly ordered and the calibration step is a genuine feedback loop, but there are no validation or verification checkpoints, and the skill explicitly offers batch operations ('handles 5 or 500 issues') — the batch-operation guideline caps workflow clarity at 3. Not 4 because the missing per-run validation is more than a minor gap given batch sizing.

3 / 5

Progressive Disclosure

Good structure with clear, well-signaled sections and an easy-to-scan layout. No bundle files exist (no references/, scripts/, or assets/), and the substantive material (formulas, research citations) is available only as remote GitHub URLs rather than bundled reference files — a minor organization gap matching anchor 4. Not 5 because the body exceeds the simple-skill under-50-lines threshold and the key detail it points to is not in the bundle; not 3 because references are clearly signaled and nothing bulky is inlined.

4 / 5

Total

13

/

20

Passed

Description

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

The description has a clear, specific 'what' aimed at a distinctive niche (AI/hybrid development estimation with PERT statistics and calibration), but it completely lacks a 'when' component — no 'Use when...' clause or trigger phrases. Its keyword coverage also misses the natural planning vocabulary (sprint, story points, sizing, backlog) that the skill's own body identifies as use cases.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g., 'Use when estimating development tasks or tickets, sprint planning, sizing a backlog, or forecasting release dates with hybrid human+agent teams.'

Include natural synonyms and vocabulary users actually say — sprint planning, story points, T-shirt sizing, backlog, capacity, forecast — rather than relying on the technical term 'PERT'.

Spell out one or two additional concrete actions (e.g., 'produces P50/P75/P90 confidence bands and calibrates against actual completion times') to lift specificity beyond a single 'estimate' verb.

DimensionReasoningScore

Specificity

'Estimate AI-assisted and hybrid human+agent development work' names the domain and one concrete action, with 'PERT statistics' and 'calibration feedback loops' as method modifiers rather than additional actions. This matches anchor 3 (domain plus 1-2 concrete actions); not 4 because it does not list several specific actions like the anchor-4 example does.

3 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

'Estimate', 'AI-assisted', 'hybrid', and 'development work' are relevant keywords, but common natural phrases users would say — 'sprint planning', 'story points', 'sizing', 'backlog', 'how long will this take', 'forecast' — are absent even though the body lists them as use cases. Matches anchor 3 (some relevant keywords, missing variations/synonyms); not 4 because the gaps are more than a few missing terms.

3 / 5

Distinctiveness Conflict Risk

'AI-assisted and hybrid human+agent development work' with 'PERT statistics and calibration feedback loops' carves a clear niche distinct from generic estimation skills, with only minor overlap risk against closely related planning/velocity skills. Anchor 4 fits better than 3, which implies broader overlap with similar skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/progressive-estimation/SKILL.md

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.