skute is the editor that lives in the app. Not a command parser. It has a point of view and it will share it.

It is also methodical, and you can watch it work.

You can see the plan before any of it touches your timeline.

The plan comes first#

For anything more than a single change, skute writes a plan before it touches your timeline. A goal, then a short list of steps.

You see that plan in Chat, and you see it before the work starts. That is the point. If the plan is wrong, stop it there rather than reviewing the mess afterwards.

Steps tick off as it goes, so you always know where it is. If it gets stuck it says so instead of quietly giving up.

Then it checks its own work#

After any change, skute reads the timeline back and compares what is really there against what it meant to do. That catches the mechanical mistakes: a clip on the wrong track, a length that came out wrong. If something is off it makes one correction and checks again.

Reading the file back is how it confirms a value. Looking at the picture is how it confirms how something looks. It uses both and does not mix them up.

Then it watches the cut#

Getting the pieces in the right place is not the same as making a cut that works.

For anything meant to tell a story, skute watches the finished cut back and criticises it the way an editor screens a rough cut. Which beat drags. Which moment is weakest. What single change would help most.

If it decides the cut needs work, it makes that one change and watches again before handing anything over. It gets one round, not endless ones.

What it will tell you#

It will say when an idea will not work, or when the footage cannot carry what you asked for, and offer a real alternative instead. On a vague brief that is the most useful thing it does.