Home / Reports / pester-should-migration

pester-should-migration

Validated 3 Aug 2026 · Repository
PRO
89
Good
0 critical
1 warnings
6 suggestions
101 passed
Domain scores
Anti-Slop
100
Accessibility
100
Enterprise
100
Issues

Warnings (1)

19.5-pipeline-no-stagesline 7
Pipeline pattern detected but no stage documentation found
Fix: Document the pipeline stages, checkpoints, and data flow between stages

Suggestions (6)

17.2-no-output-contractline 7
No output contract found; unclear what the skill produces
Fix: Document what the skill produces (format, structure, side effects)
3.4-gerund-namingline 2
Skill name could use gerund form for clarity
Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
18.1-no-confidence-signalline 1
No confidence signal found for orchestrator decision-making
Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
4.2-ambiguous-termline 29
Ambiguous term 'some' found
Fix: Replace with specific, measurable criteria
4.2-ambiguous-termline 35
Ambiguous term 'several' found
Fix: Replace with specific, measurable criteria
9.5-desc-tokensline 3
Description is 110 tokens; aim for under 100
Fix: Make description more concise
Badges
skillcheck passed skillcheck antislop 100 skillcheck WCAG AA skillcheck WCAG AAA skillcheck enterprise
Ship with confidence

Get a report like this for your own skill

Run the free validator to see your structural score, then unlock the substance checks — anti-slop, security, accessibility, agent-readiness — that move a skill from valid to safe to ship.