version: "1.0.0" name: co-op-game-intro-generator description: "Create one two-player game menu and opening animation from supplied inputs. Use when the distinct result and its preservation contract matter; unlike generate-video (relationship 0.68), choose this when two-player game menu and opening animation is requested; choose generate-video for its narrower existing outcome. Do not use for generic media, source-provider tooling, generic publication planning, or unverified capabilities."

Co-op Game Intro Generator

Catalog

• Display name: Co-op Game Intro Generator
• Categories: Video
• Status: Ready
• Route label: Independent outcome contract
• Tone: purple
• Short description: Produce one two-player game menu and opening animation with explicit inputs, boundaries, and acceptance checks.

What this skill does

• Captures the specific requested outcome and supplied asset roles.
• Produces a reviewable plan before media routing.
• Hands only approved atomic work to currently verified native Atoms.

How to use

Provide the desired result, supplied inputs, preservation requirements, ratio/duration when relevant, and acceptance criteria.

Example

Create one two-player game menu and opening animation from my supplied assets; preserve the stated facts and show the plan before media generation.

Workflow

1. Confirm the user-visible outcome, supplied inputs, fixed facts, delivery format, and exclusions.
2. Produce a concise plan and continue through the requested supported route without a client-side payment confirmation.
3. Select the narrowest verified existing Atom for any media operation; use only its live schema and never hard-code source-provider models or tools.
4. Persist one durable operation key for each intended run, poll receipts, and surface the API outcome as returned.
5. Review the requested preservation facts, output scope, ratio/duration, visible quality, and unwanted text or unsupported claims. Repair only the failing stage.

User-facing output

• Media type: One two-player game menu and opening animation
• Default quantity: 1
• Content per artifact: Approved plan, requested deliverable, and acceptance result
• Default layout: User-requested format
• Model policy: Existing verified native Atoms only
• Downstream use: Review, assembly, or publication according to the API result, without client-side confirmation