Update to PixVerse

{
  "description": "Game trailer: turn a game brief and available assets into a paced trailer with genre cues, gameplay presentation, title beats and sound.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 246
    }
  ],
  "name": "pixverse-game-trailer",
  "skill_md_contents": "---\nname: pixverse-game-trailer\ndescription: \"Game trailer: turn a game brief and available assets into a paced trailer with genre cues, gameplay presentation, title beats and sound.\"\n---\n\n# Game Trailers\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## CLI Execution\n\nApply `../../skills-shared/quality-policy.md` to all generated images/videos: Sunburst 2K/high,\nSeedance 2.5 1080p with automatic prompt enhancement, and an explicit upgrade/fallback\nchoice for Free/Basic or model-entitlement rejection.\n\nFor an explicitly selected Canvas project or node, read\n`../../skills-internal/pixverse-agent-canvas/SKILL.md` first and follow its Canvas\npreflight and delivery contract; the ordinary queue/local route below does not replace it.\n\nFor ordinary creation or editing, read `../../skills-shared/cli-workflow.md` before\nexecuting this workflow. It contains the existing account-aware routing, paid-work\nconfirmation, progress, preview and project-handoff rules. Studio and Production are\nnot prerequisites. The shared account, confirmation and direct-medium rules govern the\nexamples and defaults below. Read the gateway only when writing manual CLI commands or queue specs.\nCreation command examples below are queue-task fragments, not permission to submit paid\n`pixverse create` commands directly.\n\nA game trailer sells the promise of play. It should show verbs, not just scenery.\n\nRead:\n\n- `../../skills-shared/cinematography.md`\n- `../../skills-shared/exploration-patterns.md`\n- `../../skills-shared/model-routing.md`\n\n## Fast Path\n\n1. Identify game genre, player fantasy, and core verbs.\n2. Choose trailer mode.\n3. Generate board or key art.\n4. Render 8-15s teaser.\n5. QA for game readability and motion energy.\n\nUse `seedance-2.5` at 1080p for both preview and final shots. Apply `../../skills-internal/pixverse-seedance-prompt-enhance/SKILL.md` before preflight; preserve the workflow-specific creative controls.\n\n## Trailer Modes\n\n- **World reveal:** environment, scale, faction identity.\n- **Combat showcase:** attacks, dodge, impact, enemy response.\n- **Ability reveal:** one mechanic made legible.\n- **Character intro:** hero silhouette, weapon, stance, power.\n- **Gameplay fake:** HUD/camera grammar suggests play.\n\n## Prompt Anchors\n\nUse game camera language:\n\n- third-person over-shoulder\n- isometric tactical\n- side-scrolling action\n- first-person inspection\n- boss arena\n- diegetic HUD\n\nDo not overuse film-only terms if the result should feel playable.\n\n## Quality Checks\n\n- does it imply actual gameplay?\n- are scale and objective readable?\n- is UI present only when intended?\n- does motion show a verb?\n- does it avoid generic fantasy splash art?\n"
}