agentleFS
bloxy-studiosbloxy-studios/shorts-studio/skills/quality-check/SKILL.md

quality-check

Skill0 starsChanged 42 days agoMITView on GitHub

Internal — audiovisual QA of a rendered short. Runs measured checks (delivered spec, full decode, frame count, loudness and true peak after AAC, END-length stems, caption sync against the final voice track, caption bounds vs platform guides and faces, black/frozen frames, blank tail) and requires your inspection of the generated frame sheets before anything is called passed.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read renders/<rid>/qa.json findings and the sheets qa/contact.jpg (whole video incl.

    line 17
  2. Very specific:

    Never say "QA passed" from an exit code alone.

    line 25

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Quality check (internal)

  1. render already runs QA. To re-run: shorts-studio qa <project> --clip <id> [--render rNNN].
  2. Read renders/<rid>/qa.json findings and the sheets qa/contact.jpg (whole video incl. first/last frames) and qa/cuts.jpg (frames either side of every cut/layout join).
  3. Inspect: framing (faces, headroom, the right person), captions (legible, not over faces/UI, emphasis meaningful, none stale), cut smoothness, colour, graphics landing frames, anything broken. Record it: shorts-studio qa note <project> --clip <id> --render <rid> --what "..." --notes "...".
  4. Each failing finding names a repair rule; apply it with /shorts-studio:revise, re-render, re-check. Stop after the project's repair budget and deliver honestly as draft/blocked.

Never say "QA passed" from an exit code alone. Full real-time playback is not possible here; say so and point the user to preview_540x960.mp4.

Completion: qa.json verdict recorded, every sheet inspection recorded (agent-visual), and remaining failures listed in the report.

Download now (ZIP)

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.