Home / Reports / skill-creator

skill-creator

Validated 8 Jul 2026 · Repository

PRO

Poor

0 critical

10 warnings

21 suggestions

78 passed

Domain scores

Anti-Slop

100

Accessibility

100

Enterprise

100

Issues

Warnings (10)

16.1-no-stop-conditionline 6

Complex skill lacks explicit stop conditions

Fix: Add stop/termination criteria (e.g., 'Stop after N iterations', 'Abort if error rate exceeds threshold')

15.1-no-budget-capline 6

Multi-agent skill has no budget or turn cap; runaway costs are possible

Fix: Add max_turns, cost_limit, or similar budget constraint for subagents

19.3-generator-no-output-specline 6

Generator pattern detected but no output format specified

Fix: Document the output format (template, schema, or example output)

19.2-reviewer-no-criterialine 6

Reviewer pattern detected but no evaluation criteria documented

Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)

13.1-dangling-referenceline 369

File reference does not exist on disk: /tmp/eval_review_

Fix: Verify the path or remove the stale reference

13.1-dangling-referenceline 410

File reference does not exist on disk: .skill

Fix: Verify the path or remove the stale reference

13.1-dangling-referenceline 426

File reference does not exist on disk: .docx

Fix: Verify the path or remove the stale reference

13.1-dangling-referenceline 426

File reference does not exist on disk: .xlsx

Fix: Verify the path or remove the stale reference

7.7-task-ambiguityline 294

Ambiguous instruction detected (subjective-quality)

Fix: Add measurable criteria (e.g., 'reduce to <20 lines', 'under 100ms')

9.2-body-tokens-warningline 6

Body exceeds 5000 token optimal budget (estimated 6696)

Fix: Consider condensing or using references

Suggestions (21)

16.3-no-rollbackline 6

State-modifying skill lacks rollback or recovery guidance

Fix: Add rollback instructions: how to undo changes if something goes wrong (e.g., git revert, backup/restore steps)

16.4-no-idempotencyline 6

Skill does not document whether it is safe to re-run

Fix: Add idempotency guidance: state whether running the skill twice produces the same result or causes side effects

17.4-no-interface-sectionline 6

Input and output contracts exist but lack a dedicated interface section

Fix: Add a ## Interface or ## I/O section to consolidate contract documentation

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)

4.2-ambiguous-termline 14

Ambiguous term 'few' found