Home / Reports / algorithmic-art

algorithmic-art

Validated 5 Jun 2026 · Repository

PRO

Needs Work

0 critical

3 warnings

15 suggestions

92 passed

Domain scores

Anti-Slop

Accessibility

100

Enterprise

100

Issues

Warnings (3)

5.1-no-style-sectionline 1

No writing style section found

Fix: Add a '## Writing Style' or '## Anti-Slop' section

16.1-no-stop-conditionline 7

Complex skill lacks explicit stop conditions

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

19.2-reviewer-no-criterialine 7

Reviewer pattern detected but no evaluation criteria documented

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

Suggestions (15)

5.2-no-do-dontline 1

Missing DO/DON'T lists for style guidance

Fix: Add explicit DO and DON'T lists for writing patterns

16.4-no-idempotencyline 7

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

12.8-missing-feedback-loopline 7

Quality-critical skill lacks a validation step

Fix: Add a verify/validate step after the main operation (per best practices: run validator, fix, repeat)

17.4-no-interface-sectionline 7

Input and output contracts exist but lack a dedicated interface section

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

14.3-no-binary-verdictline 1

Skill has success criteria but no binary pass/fail language

Fix: Add explicit pass/fail indicators so evaluators reach the same verdict independently

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.2-no-progress-signalline 1

Complex skill lacks progress reporting checkpoints

Fix: Add progress signals (e.g., 'Step 2 of 5: validating input') for long-running workflows

18.3-no-structured-outputline 1

No structured output format defined for machine consumption

Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results

4.2-ambiguous-termline 24

Ambiguous term 'some' found