task-estimation
Estimate software development tasks accurately using various techniques. Use when planning sprints, roadmaps, or project timelines. Handles story points, t-shirt sizing, planning poker, and estimation best practices.
Install with Tessl CLI
npx tessl i github:supercent-io/skills-template --skill task-estimation85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It clearly specifies what the skill does (estimation using various techniques), when to use it (sprint/roadmap/timeline planning), and includes domain-specific trigger terms that users would naturally employ. The description is concise yet comprehensive, following the recommended pattern of good examples in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Estimate software development tasks', 'planning sprints, roadmaps, or project timelines', and specific techniques like 'story points, t-shirt sizing, planning poker, and estimation best practices'. | 3 / 3 |
Completeness | Clearly answers both what ('Estimate software development tasks accurately using various techniques', 'Handles story points, t-shirt sizing, planning poker') AND when ('Use when planning sprints, roadmaps, or project timelines') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'estimate', 'sprints', 'roadmaps', 'project timelines', 'story points', 't-shirt sizing', 'planning poker'. These are terms developers naturally use when discussing estimation. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on software estimation with distinct triggers like 'story points', 't-shirt sizing', 'planning poker' that are unlikely to conflict with other skills. The domain is well-defined and specialized. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable estimation guidance with concrete examples and a useful TypeScript risk adjustment function. However, it's somewhat verbose with unnecessary metadata, empty example placeholders, and could benefit from better progressive disclosure by splitting detailed reference content into separate files. The workflow lacks explicit validation/feedback loops for comparing estimates to actuals.
Suggestions
Remove the empty Examples section placeholders and the Metadata section (version, tags, platform compatibility) which don't add actionable value
Add a validation step for comparing estimates against actual completion times to create a feedback loop for improving future estimates
Move the detailed story point definitions and T-shirt sizing tables to separate reference files, keeping only a quick reference in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the metadata section with version/platform info, empty example placeholders, and external reference links that don't add actionable value. The core estimation content is well-structured but could be tighter. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific story point definitions, a working TypeScript function for risk adjustment, detailed Planning Poker process steps, and a complete estimation document template that's copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced (Step 1-4), but lacks explicit validation checkpoints. For estimation workflows, there's no feedback loop for verifying estimates against actuals or adjusting based on velocity data, which would strengthen the process. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections but is somewhat monolithic. The detailed story point breakdown, Planning Poker process, and T-shirt sizing could be split into separate reference files. External links are provided but internal progressive disclosure is weak. | 2 / 3 |
Total | 9 / 12 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.