review-cut-videos
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Reviews and improves actual cut playback; stops before final assembly. Use only when the user asks for a video review.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- autoproduceSkill
- brandingSkill
- channelSkill
- compose-blenderSkill
- datagoSkill
- edit-speechSkill
- generate-cut-imagesSkill
- generate-cut-videosSkill
- grow-instagramSkill
- grow-threadsSkill
- grow-youtubeSkill
- ingestSkill
- inspect-contentSkill
- introSkill
- platform-guideSkill
- produceSkill
- project-initSkill
- publishSkill
- review-cameraSkill
- review-contextSkill
- review-cut-imagesSkill
- review-recentSkill
- setup-instagramSkill
- setup-threadsSkill
- setup-youtubeSkill
- storyboardSkill
- topic-scoutSkill
- upscale-videoSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Follow the production order.
- Distinctive: line 14
Read host review. Give an independent reviewer the real clips, reviewed images and direction plan.
- Distinctive: line 19
Use actual playback. Sampled frames establish composition only.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Cut Videos
Runs only when the user asks for it (user directive 2026-10-31); no other step waits on it. Follow the production order.
Read host review. Give an independent reviewer the real clips, reviewed images and direction plan. Review all clips and their intended sequence for cause/effect, action timing, physical contact, camera path, focus, prop state, identity and continuity. Name defects by time and consequence, with the smallest repair.
Use actual playback. Sampled frames establish composition only. If playback or independent review is unavailable, report the limitation; never convert not_reviewed into pass. Speech/audio judgments require actual listening when requested, and no automated STT or speech-scoring loop is introduced.
The author returns to the earliest defective layer and preserves failed clips and reports. Retry generation only within authorized attempt/spending limits and the user's approval of each new plan. Recheck corrected clips and affected joins independently, and name the actual video files the report covers. This stage does not publish.
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.

