Axis Desk

Work out whether a shot list actually cuts together. Editing grammar is arithmetic on ADJACENT PAIRS, which is why almost nobody checks it: a jump cut is a property of two rows of a shot list and of nothing else in the document, so a person reading one row at a time will never find one. Three machines, all decidable from fields a shot list already has. The size lattice - els < ls < mls < ms < mcu < cu < ecu - where two shots of the SAME subject fewer than two steps apart, from an angle that has moved less than thirty degrees, is a jump cut; two shots of different subjects at the same size are an ordinary reverse and are never reported. The 180-degree line, where a cut from one side of the axis to the other with no neutral shot between them reverses screen direction, so two people talking appear to face the same way - and one shot on the wrong side produces TWO illegal cuts, one at each end. And coverage: no wide is no geography, no close is no moment, all mediums is neither and is what a day without a shot list produces. It also reports which cuts it could NOT examine, because a clean report over a list missing half its fields is worse than no report. The two-step and thirty-degree thresholds are conventions rather than derivations; the arithmetic on top of them is exact, and the app reports the two differently. Five lanes: cover, check, repair, eyeline and order. The engine is free and runs in the browser. Lanes derived from coreyhaines31/marketingskills (MIT), whose video skill covers producing video with AI tools and programmatic frameworks. Not affiliated with or endorsed by coreyhaines31.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.