agentleFS
trku052-pngtrku052-png/social-media-youtube-skills/skills/23-vibe-editing-review/SKILL.md

vibe-editing-review

Skill1 starsChanged 3 days agoLicence not identifiedView on GitHub

Use this skill when a rendered video must be checked before it is published or handed over: does it match the brief (size, frame rate, duration), the approved edit and the script; are there black or frozen frames, dropped sound, long silences, clicks, loudness or true-peak problems; do the captions follow the final timeline, keep to line and reading-speed limits and spell names right; is private data visible. It scans the file read-only with FFmpeg, guides one full viewing with sound, and writes a report with output times, evidence and fixes, plus what it could not check. Also for diagnosing a broken render, writing the handoff for another agent, and turning an accepted video into a template for a series. Not for making the cut (vibe-editing-cut), or validating and rendering HyperFrames or Remotion projects (hyperframes-cli, remotion-render).

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.