Plan and render a self-contained marketing video through hosted HyperFrames or Remotion, inspect the terminal result, and return verified video assets.
Plan and render a self-contained marketing video through hosted HyperFrames or Remotion, inspect the terminal result, and return verified video assets.
# Programmatic Marketing Video ## Loadout capabilities Render a complete self-contained compositionHtml through the hosted runtime. Use <action-tag>cli:hyperframes:render</action-tag>. Required for this workflow. Render complete entryPointSource with an exact compositionId when the user selects Remotion instead. Use <action-tag>cli:remotion_cli:render</action-tag>. Optional for the selected branch. ## Purpose and scope Plan and render a self-contained marketing video through hosted HyperFrames or Remotion, inspect the terminal result, and return verified video assets. This is a newly authored Loadout workflow adaptation of the pinned upstream Skill, not an unchanged import. Its supported scope and changes are recorded in [provenance](UPSTREAM.md). Read [supporting files](SUPPORTING-FILES.md) progressively. ## Render workflow 1. Collect the brief and choose HyperFrames unless Remotion is specifically appropriate. Read [the method](METHOD.md) and resolve the chosen Action's current schema and readiness before execution. 2. Produce a storyboard and a complete composition that fits the supplied brief and input schema. Explain unprovided media/audio and use a typography-only composition when those assets are unavailable. 3. Preflight the exact Action input, then execute the chosen hosted renderer separately through Loadout. Do not include an executable file in this public Skill package. 4. Inspect the terminal render output and delivered assets. Follow the method's output checks. Do not treat acceptance, provider success flags without an artifact, or an empty asset list as a completed video. 5. Return the verified MP4 asset and the render specifications, or a specific runtime blocker. A retry requires a corrected input or a diagnosed transient failure; repeated unchanged failures are not progress. ## Acceptance and failure boundaries Apply [acceptance criteria](ACCEPTANCE.md). If a required Action cannot resolve or the account is not connected, stop before writes and report the specific setup blocker. Never infer execution from guidance alone.
