Daytona Recording Artifacts

Use this skill to collect proof that a Daytona UI flow works. Use daytona-flow-validator before declaring the flow passed. If the user asks to do e2e tests for a feature, frame proof is required unless they explicitly ask for non-UI or mock-only validation.

Default: Frame-by-Frame HTML Proof

The default proof format is a browseable HTML page with named PNG screenshots for each step of the flow. This is faster to produce, easier to review, and works on any device.

Use video (MP4) only when the proof requires motion: streaming text, loading spinners, animations, drag-and-drop, or real-time interactions that a static frame cannot capture. When video is used, embed it inside the frame-by-frame HTML page alongside the static frames.

When a coded eval exists, prefer the eval runner frame output first: