Update to PixVerse

{
  "description": "Video variants: produce many versions of one generated video project by swapping the host, product, wording, language, aspect or hook while reusing every accepted asset and regenerating only what changes.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 312
    },
    {
      "relative_path": "references/reuse-matrix.md",
      "size_in_bytes": 1494
    }
  ],
  "name": "pixverse-video-variants",
  "skill_md_contents": "---\nname: pixverse-video-variants\ndescription: \"Video variants: produce many versions of one generated video project by swapping the host, product, wording, language, aspect or hook while reusing every accepted asset and regenerating only what changes.\"\n---\n\n# Video Variants\n\nWhen this workflow generates images or video, apply `../../skills-shared/quality-policy.md`:\nSunburst 2K/high for images, Seedance 2.5 1080p with automatic prompt enhancement for video,\nand a stopped upgrade/fallback choice for Free/Basic or model-entitlement rejection.\n\nOne editable production, many deliverables. A variant changes one or a few roles (host,\nproduct, wording, language, aspect, hook) and reuses everything else: accepted images,\ntakes, music, graphics, timeline and plan. Paid work is only the parts that actually change.\nOrdered edits of a supplied ad stay in `../pixverse-ad-variants/SKILL.md`.\n\n## Installed Command\n\nBefore running helper commands, resolve the absolute plugin root from this `./SKILL.md` path: it is two directories above this skill directory and contains `.codex-plugin/plugin.json`. In every new shell session, set:\n\n```bash\nPVX=\"<absolute-plugin-root>/scripts/pvx\"\n```\n\nRun helper commands through `\"${PVX}\"`. Do not assume the user's current working directory is the plugin checkout, and do not bypass the installed wrapper with a module invocation.\n\n## Define The Variant Sheet\n\nStart from an existing project with its script, timeline, plan and manifest. For each\nvariant record: the change (what and where it appears), the assets that stay, the assets to\nregenerate, and the acceptance check. Zip ordered lists; never build a Cartesian product the\nuser did not ask for. Read `./references/reuse-matrix.md` for what each change touches.\n\n## Reuse Before Generating\n\nCarry accepted assets into the new queue without paying again:\n\n```bash\n\"${PVX}\" queue append projects/<slug>-v2/queue.json --project <slug>-v2 --id broll-leaves --reuse <slug>:broll-leaves\n\"${PVX}\" queue append projects/<slug>-v2/queue.json --id host-cat --reuse <slug>:host-cat\n\"${PVX}\" queue append projects/<slug>-v2/queue.json --id take --preflight -- pixverse create reference --model seedance-2.5 ... --images \"{{host-cat.path}}\" --prompt ...\n```\n\n`--reuse <project>:<task-id>` copies the accepted asset's provider path and local file from\nthat project's manifest; the preflight lists it as reused with no charge and dependents can\nreference `{{id.path}}` as usual. Generate only the changed nodes: a new host image and its\ntakes for a host swap, new takes for new wording, a new voice and takes for a language,\nnew inserts for a product. Graphics with the swapped identity (an avatar in a sticker, an\nicon on a board) are re-rendered locally, not regenerated.\n\nThe example assumes `host-cat` is already an accepted source-project asset; otherwise\ngenerate the new host image before referencing it. The identifier after the colon is the\nqueue task key, not a provider generation ID. The helper selects its latest successful\nmanifest entry; it cannot infer creative acceptance or rejection. Verify the selected task\nID against project decisions before reuse, and use a distinct task key for rejected retakes.\n\n## Re-flow The Composition\n\nRebuild the timeline from the new takes (`../../skills-shared/word-timing.md`); anchors,\ncaptions, boards and sounds follow the new words. Re-render the plan\n(`../../skills-shared/anchored-composition.md`) with only the changed sources swapped. For\nan aspect change, keep the script and takes when the framing allows it and adapt the plan\ngeometry; regenerate takes only when the composition truly needs a different frame.\n\nTiming re-flow does not relocate graphics around a new face, prop or gesture. Inspect the\nnew take at the overlay anchors and re-place cards, boards, inserts and stamps before the\nfinal render. Reuse the layout only after checking its occupied regions on the new host.\n\n## Deliver As A Set\n\nSample one grid per variant on the same anchors and compare. Deliver the files with a\ncompact sheet: variant, what changed, what was reused, task ids and credits from the ledger.\nRepair only the rejected variant. Keep the project editable so the next batch starts from\nthe same accepted base.\n\n## Execution\n\nRead `../../skills-shared/production-brief.md` for reference roles, prompt construction and revisions.\nFor media execution, follow `../../skills-shared/cli-workflow.md`; load the gateway before manual\nCLI commands or queue specs. Local media, script, timeline and graphics commands spend no credits.\nPrompt-only work ends with the usable plan and prompts; it needs no account or generation calls.\n"
}