agentleFS
Sign inStart free
harshil-1411harshil-1411/claude_plugin_video_studio/skills/test/SKILL.md

test

Skill0 starsChanged 47 days agoApache-2.0View on GitHub

Golden-frame regression test for a rendered video-studio project - samples frames of the reel (first frame, each scene's midpoint, last frame), compares them with the golden frames stored in the project's golden/<quality>/ folder by SSIM, and records new goldens after the render has been checked by eye. Use when the user runs /video-studio:test, asks whether a re-render still looks the same, or wants to lock in a render as the reference.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use the project folder the user named, else the cwd (absolute path).

    line 15
  2. Distinctive:

    Never record goldens without looking first: they become the reference every later render is judged against.

    line 32
  3. Very specific:

    Check the render by eye: Read a few frames (for example the cover or thumbnail in dist/, or the frames from a previous qa/test-frames/ run) …

    line 35
  4. Very specific:

    Read two or three of the recorded PNGs in golden/<quality>/ to confirm they show the intended frames, then tell the user to commit golden/.

    line 40
  5. Distinctive:

    When a failure is an intended change (new copy, new brand, a renderer upgrade), re-record the goldens the same way.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 154 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

Golden-frame test

Golden frames are small PNGs of a known-good render, kept in the project at golden/<quality>/ with golden.json (sample times, frame width, SSIM threshold, reel and spec hashes). Commit them with the project.

  1. Use the project folder the user named, else the cwd (absolute path). It needs a render (renders/<quality>/); if there is none, say so and offer the render skill.
  2. Call mcp__plugin_video-studio_engine__test {project_dir} (add quality: "preview" or "final" to pick a render; the default is the latest).
  3. Report the status:
    • pass: every sampled frame matches its golden (SSIM at or above the threshold).
    • fail: list each failing frame with its SSIM. Read the images it names under qa/test-frames/ (*.diff.png shows golden | current | difference) and describe what changed. A size, fps or timing change fails before any frame is compared; say which.
    • missing: there are no goldens yet for this quality.

Recording goldens (update: true)

Never record goldens without looking first: they become the reference every later render is judged against.

  1. Check the render by eye: Read a few frames (for example the cover or thumbnail in dist/, or the frames from a previous qa/test-frames/ run) and confirm with the user that the render looks right.
  2. Call mcp__plugin_video-studio_engine__test {project_dir, update: true} (same quality as the render being recorded).
  3. Read two or three of the recorded PNGs in golden/<quality>/ to confirm they show the intended frames, then tell the user to commit golden/.

When a failure is an intended change (new copy, new brand, a renderer upgrade), re-record the goldens the same way; otherwise treat it as a regression and use the diff skill against a known-good render to find the cause.

The full report is in qa/test.md (machine-readable: qa/test.json).

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.

Check your setup, free