AB work-estimation-en
Software Development Work Estimation Skill. Triggered when user mentions "work estimation", "project estimation", "effort estimation", "timeline assessment", "task breakdown", "man-hour calculation", "development cycle", or similar terms. Accepts user requirements text or documents, automatically breaks down work items and estimates effort, outputting Excel evaluation reports.
As a process B 71/100 · Nearly there — weak spots: failures and branches, consistency, progress reporting
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 71/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (work-estimation-en) differs from the folder (work-estimation)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 758 tokens
- 100Running it twice. No mutating operations
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 379: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.