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.
86
82%
Does it follow best practices?
Impact
91%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 uses proper third-person voice and maintains a clear, distinct niche.
| 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 trigger guidance. | 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 estimation techniques 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 specific to agile estimation. | 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 useful templates. However, it's overly verbose with redundant sections (story points and T-shirt sizing overlap), includes unnecessary metadata/tags, and has empty placeholder sections. The workflow lacks validation steps for verifying estimates against actual outcomes.
Suggestions
Remove the empty 'Examples' placeholders at the end or fill them with actual worked examples
Consolidate story points and T-shirt sizing into a single reference table to reduce redundancy
Remove the Metadata section (version, tags) as this adds no actionable value for Claude
Add a validation step: 'After sprint completion, compare estimates to actuals and adjust future estimates accordingly'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful content but is verbose in places. The metadata section, empty example placeholders, and extensive markdown formatting add unnecessary tokens. The story point guidelines and T-shirt sizing sections overlap conceptually. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific examples (Planning Poker scenario, TypeScript code for risk adjustment), clear point scales with real-world task examples, and a complete output template that's copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Steps 1-4), but there are no validation checkpoints or feedback loops. For estimation tasks, there's no guidance on what to do if estimates prove wrong or how to validate estimates against historical data. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but everything is inline in one file. The external references section links to external sites rather than companion files. The empty example placeholders suggest incomplete organization. | 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.