Read-Only Legacy Remotion Render Verification

Where this fits

You're maintaining a pipeline that predates v0.9. A customer asks you to confirm whether a render from six months ago was actually delivered correctly. You can't re-run Remotion—the environment is gone, and you must not touch the new v1 production path. You need an agent that can inspect the existing manifest, receipt, and media hash, and give a verdict without launching anything. That's the exact scenario broll-remotion-render was built for.

Why agents benefit

• Zero side effects: The skill never installs Remotion, opens Studio, or triggers a render—it only reads and verifies existing records.
• Deterministic verification: It checks that source, dependency lock, Composition ID, lint, and approval share one unchanged identity, plus hash and FFprobe facts.
• Distinguishes valid production from failed attempts: It rejects partial or retry artifacts that were never officially approved.
• Safe for legacy recovery: It can recover delivery details from old manifests without upgrading or re-rendering.
• Explicit guardrails: The skill's README forbids dispatching in new v1 production, keeping agents from accidentally corrupting current workflows.

Practical scenarios

Auditing an old render before migration

You're moving from pre-v0.9 to v1 and need to prove which old renders are trustworthy. The agent reads each manifest and verifies hash and duration against the recorded receipt, flagging any mismatches.

Recovering a lost delivery artifact

A client lost the final video file but still has the render receipt. The agent cross-checks the receipt with the master manifest and media verification, confirming the exact file hash so it can be re-sourced from backup.

Verifying a third-party claim

A contractor claims they delivered a valid render for a pre-v0.9 task. The agent inspects the existing evidence and reports whether the claim matches the recorded production facts, without re-rendering anything.

Add it to your agent workflow

Install the skill with:

npx skills add erduo1998-cell/erduo-broll-loop-engineering --skill broll-remotion-render

Then instruct your agent to call it when a user asks to inspect or recover an old task. Example prompt:

Verify the render receipt in ./legacy/2024-03-14/ against the master manifest. Do not install or run Remotion.

The agent will follow the skill's read-only checks and return a structured verdict.

Compare before adopting

Before adding this skill, compare it with alternatives: does it match your legacy record format? Check the GitHub repo's last commit date, issue responses, and star count (165 stars suggests community use). Also compare with a manual script you might write—if your records are few and static, a one-off script may suffice. But if you expect agents to handle varied legacy tasks, this skill's guardrails are valuable.

Why it is worth tracking

This skill addresses a real pain point: safely handling legacy production records without risking new workflows. Its explicit “never dispatch in v1” rule and read-only design make it a model for compatibility skills. The 165 stars and active maintenance signal community trust. Track it if you run mixed-version pipelines or need audit trails for old renders. For a full overview, see the skill page at https://www.openagentskill.com/skills/erduo1998-cell-broll-remotion-render and evaluate it when your next legacy recovery request arrives.