makinari-rol-judge-slides

To automate per-slide evidence verification, apply a judge skill to reveal.js or spectacle-based presentation decks. The process enforces evidence collection for each slide and validates that acceptance tokens like deck title, slide count, and key sections are present in the evidence.

Yes, automated slide acceptance checks support both reveal.js and spectacle-based presentations. The validation process checks that each slide has a corresponding screenshot-capture tool-call and verifies deck-level acceptance tokens to ensure presentation readiness.

Per-slide evidence collection in QA workflows is the process of capturing and validating screenshots for each individual slide within a presentation deck. It enforces acceptance-token matching to ensure every slide meets required criteria before deck approval.

Validating presentation-ready decks requires a reveal.js or spectacle-based presentation deck and defined acceptance tokens like deck title, slide count, and key sections. A screenshot-capture tool-call must exist for each slide to generate the necessary evidence for validation.

Slide decks fail acceptance token matching during QA when required tokens like deck title, slide count, or key sections are missing from the collected evidence. Verification also fails if a screenshot-capture tool-call does not exist for every individual slide.