check-render
Skill4 starsChanged 9 days agoMITView on GitHub
Verify a rendered video before handing it over — decodes every frame and reports frozen stretches, black gaps, hard cuts to black at the end, an intro that doesn't animate, wrong duration, low bitrate and missing audio. Use it after every render of an edit, and whenever the user says the video "lags", "drops frames", "freezes", "is static", "cuts off at the end" or looks low quality.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- berkayburakk/tubecrewtheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- berkayburakk/tubecrew★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- analyze-referenceSkill
- filmcraft-editingSkill
- match-gradeSkill
- photo-titleSkill
- recap-editSkill
- select-shotsSkill
The file
Files
Checking a render
A few spot frames miss most real problems: a clip that freezes for half a second, an intro image sequence that rendered as a still, a Dip to Black that hard-cuts instead of fading (viewers call it lag), a 20 Mbps export when 40 was wanted. Check the whole file.
python3 ${CLAUDE_SKILL_DIR}/scripts/check_render.py out.mp4 --intro-frames 105 --expect-seconds 39.8 \
--min-mbps 15 --fade-frames 50Needs Pillow and FILMCRAFT_CLI="${user_config.filmcraft_cli}". Exit code 1 means fix something;
problems says what and where (frames and seconds). --keep <dir> keeps the decoded frames for a
look (or for match-grade).
Reading the results and fixing
| Problem | Usual cause | Fix |
| frozen inside the edit | source clip shorter than its slot, a still where a clip should be, a stale image sequence | check the shot's in-point + length; bake sequences (import_media bake=true) |
| intro does not animate | the app kept old frames of a re-written image sequence | write frames to a new folder, bake to .mov, re-import |
| ending: cuts to black | Dip to Black on the last clip | fade (opacity keyframes) on the last shot and the caption |
| black gaps | a hole between clips, a missing clip (offline media) | list_timeline; re-place the clip |
| low bitrate | default export | render(bitrateMbps: 30-40) |
| no audio stream | music placed with audio: false, or noAudio | place the soundtrack on A1 |
"Laggy" can also mean 24 fps clips judder in a 30 fps edit (frame blending fixes it) or the viewer's player struggling with a high bitrate — frozen-frame analysis tells these apart from real drops.
Then look at frames from each section yourself, and tell the user what you verified and what you couldn't (listening to the audio).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

