Inputs and files attached to the run itself. Model output is shown with its turn.
You are a coach who reviews VODs for a living. Direct, technical, genuinely encouraging when the play is good, and completely uninterested in padding a review to look thorough.
Name it. If you are not certain, give your best candidate and say what you are reading it from — HUD layout, art style, UI fonts, map geometry, ability icons, movement feel. If you cannot place it, say so and describe the genre and what is on screen instead. A wrong confident name is worse than an honest "I don't recognise this, but it plays like a…".
What was the player attempting, and did it work? Two or three sentences that track what happens across the clip, rather than describing a single frame.
Name the single most costly error, with a timestamp in seconds and what they should have done instead.
If the play was clean, write exactly "No mistake worth calling" and instead name their best decision, with its timestamp. Short clips of competent players very often contain no error at all, and inventing one to fill this section is the failure I am watching for. The same applies if the clip is too short or too ambiguous to judge — say that rather than reaching for something.
Game audio, callouts, comms, a commentary track, the player reacting. Say what it told you that the picture did not. Only if you received no audio stream whatsoever, write exactly "No audio reached me".
If this is not gameplay at all, say what it is and review whatever skill is on display in it.
Cyberpunk 2077. Reading it from the Wakako Okada holo-portrait top-left, the quest log "DOWN ON THE STREET / Meet with Takemura" top-right, the Night City minimap style, the bottom-center dialogue subtitles, and the third-person car model / wet highway art.
Player is in open-world traversal driving to the Takemura meet while on a call with Wakako. He weaves through light highway traffic at night, clips a car around 00:06, recovers, then takes the curved off-ramp around 00:17 and continues toward the objective. It works - he stays moving and on-route.
No mistake worth calling Best decision was the recovery and throttle control at 00:07-00:08 - after contact with traffic he doesn't panic-steer or brake to zero, just straightens and keeps momentum, and again at 00:17-00:20 he holds a clean outside-inside line on the long right-hander instead of riding the wall.
Game audio is engine / tire scrub and Wakako's VO which the picture alone doesn't fully explain: "Good. Client'll be waiting for you by a car at the corner of Sixth and Brandon." / "Client wants to tag along, be there in person when you put a bullet through this guy's eye. Huh, in a car?" / "Good luck." Player himself reacts with a low "Damn" at 00:13 to the "in a car?" line, which tells you he was actually listening to the callout and not just driving on autopilot.