CtrlK
BlogDocsLog inGet started
Tessl Logo

project-sizing-guide

Software project effort estimation assistant. Outputs three-point estimates (optimistic/most-likely/pessimistic values with confidence intervals), T-shirt sizes, or Function Point Analysis (FPA) counts. Triggered when users ask 'how long will this feature take,' need to assess project workload, perform PERT estimation, T-shirt sizing, FPA, sprint planning, or quote-based effort breakdowns.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, actionable skill body that combines executable calculator examples, concrete formulas, and a clear output template with well-structured per-method workflows. It is lean and well-organized, with only minor room to tighten prose and split out the densest FPA tables.

Suggestions

Move the three FPA complexity-assessment matrices (ILF/EIF, EI, EO/EQ) into a references/ file and link to it from the FPA section to reduce body length and improve progressive_disclosure.

Trim a few rules-of-thumb sentences (e.g., the O/M/P narrative) into the existing tables to lift conciseness from 4 to 5.

Add an explicit final verification step in the Quick Start workflow (e.g., 'Re-check that adjustment factors sum and confidence intervals are reported') to strengthen the workflow checkpoint.

DimensionReasoningScore

Conciseness

Largely lean and table-driven with domain-specific data Claude does not already know (FPA weight matrices, confidence intervals); a few explanatory passages could be trimmed but every section earns its place.

4 / 5

Actionability

Provides copy-paste-ready CLI invocations covering all three methods, concrete formulas, and a complete output template — fully executable guidance for the common cases.

5 / 5

Workflow Clarity

Each method has a clearly sequenced numbered workflow plus a method-selection guide and an adjustment-factor checklist acting as a checkpoint; falls short of 5 only because there is no explicit validate→fix→retry feedback loop (not required since estimation is non-destructive).

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one real, clearly signaled bundle file (scripts/estimate_calculator.py) and a one-level reference list; minor gap is that the detailed FPA complexity matrices could arguably live in a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

100%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 model description: concise, third-person, names concrete outputs, and pairs them with a rich set of natural trigger phrases. It fully answers what and when with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete outputs — 'three-point estimates (optimistic/most-likely/pessimistic values with confidence intervals), T-shirt sizes, or Function Point Analysis (FPA) counts' — giving comprehensive coverage of capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (the three estimation outputs) and 'when' via a concrete 'Triggered when users ask...' clause listing real trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases and synonyms such as 'how long will this feature take', 'assess project workload', 'PERT estimation', 'T-shirt sizing', 'FPA', 'sprint planning', and 'quote-based effort breakdowns'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (software effort estimation) with distinct, domain-specific triggers; minimal overlap risk with unrelated skills.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.