CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

estimate

Estimate task effort from complexity, dependencies, velocity, risk. Structured estimate with confidence levels.

Quality

75%

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/estimate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a strong, highly actionable workflow: concrete Grep-based measurement commands, explicit input-validation and missing-data checkpoints, and a complete output template. Its only notable weaknesses are minor verbosity and the lack of any progressive-disclosure structure for the sizable output template.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — it gives exact tool invocations instead of explaining concepts, and every phase carries task-specific guidance. Minor instances could be trimmed (e.g. restating that Grep counts are the measurement), so anchor 4 rather than 5.

4 / 5

Actionability

Guidance is copy-paste ready: exact Grep patterns with output_mode="count" for non-blank lines and branching, sectioned reading via offset/limit, dependency signatures per language, and a complete markdown output template covering common cases. Fully executable — anchor 5.

5 / 5

Workflow Clarity

A clear Phase 1–5 sequence with explicit validation checkpoints and recovery paths: ask for clarification when the task is too vague, name files Grep could not count under Notes rather than dropping them, and prescribed handling of missing sprint data (explicit statement plus confidence-level consequence). The skill is read-only, so the destructive-operation cap does not apply — anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and the ~140-line body is well organized under clear phase headings; however, the full output template and some guideline lists are inlined where a one-level-deep reference file could hold them. Good structure with minor organization gaps — anchor 4.

4 / 5

Total

18

/

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 clearly states what the skill does and is reasonably specific about its inputs and output, but it entirely lacks a "Use when..." trigger clause and natural trigger synonyms. Adding explicit trigger guidance would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to estimate a task, size work, or asks how long something will take."

Add natural user phrasings/synonyms such as "how long", "size this task", or "story points" to broaden trigger-term coverage.

Optionally name the concrete deliverable sections (effort range, confidence, risk factors, breakdown) to strengthen specificity.

DimensionReasoningScore

Specificity

"Estimate task effort from complexity, dependencies, velocity, risk" names the domain and one or two concrete actions (estimate effort; produce a "Structured estimate with confidence levels"), but does not list several distinct actions. This matches anchor 3; it is not anchor 4 because the factor list describes inputs rather than a broader set of capabilities.

3 / 5

Completeness

The "what" is clear (effort estimation producing a structured estimate with confidence levels), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "estimate", "task effort", "complexity", and "velocity" are natural, but common user variations such as "how long", "size this task", or "story points" are missing. Some relevant keywords, missing variations — anchor 3.

3 / 5

Distinctiveness Conflict Risk

Effort estimation driven by complexity, dependencies, velocity, and risk is a distinct niche with minor overlap risk against closely related sprint-planning or task-breakdown skills. Mostly distinct — anchor 4, not 5, since it does not state explicit trigger phrases that fully separate it from adjacent planning skills.

4 / 5

Total

13

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/estimate/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.