skill-creator — SkillCheck Report

Issues

Warnings (6)

16.1-no-stop-condition Complex skill lacks explicit stop conditions line 6
Fix: Add stop/termination criteria (e.g., 'Stop after N iterations', 'Abort if error rate exceeds threshold')
2.1-lines-warning Body exceeds 500 lines (got 609) line 6
Fix: Consider condensing or splitting content
19.3-generator-no-output-spec Generator pattern detected but no output format specified line 6
Fix: Document the output format (template, schema, or example output)
13.1-dangling-reference File reference does not exist on disk: ~622 line 499
Fix: Verify the path or remove the stale reference
12.3-workflow-vague-step Step ends with vague trailing phrase: "**References** (unlimited) — As needed" line 59
Fix: Remove 'etc', 'and so on', 'as needed' - list specific items or add a separate step
12.3-workflow-vague-step Step ends with vague trailing phrase: "**Installation** — `pip install`, `..." line 104
Fix: Remove 'etc', 'and so on', 'as needed' - list specific items or add a separate step

Suggestions (8)

16.4-no-idempotency Skill does not document whether it is safe to re-run line 6
Fix: Add idempotency guidance: state whether running the skill twice produces the same result or causes side effects
17.1-no-input-contract No input contract found; unclear what data the skill expects line 6
Fix: Document what the skill expects as input (format, required fields, constraints)
17.3-no-mode-awareness Skill does not clarify standalone vs composed behavior line 6
Fix: Clarify whether the skill works standalone, in pipelines, or both
14.2-no-examples No input/output examples found line 1
Fix: Add example input/output pairs or <example> blocks to make the skill testable
3.4-gerund-naming Skill name could use gerund form for clarity line 2
Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
18.1-no-confidence-signal No confidence signal found for orchestrator decision-making line 1
Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
4.2-ambiguous-term Ambiguous term 'appropriate' found line 339
Fix: Replace with specific, measurable criteria
4.2-ambiguous-term Ambiguous term 'appropriate' found line 492
Fix: Replace with specific, measurable criteria