Assembly One-Step Clip

Problem

Seller or listing teams often already have authorized assembly stills but need short clips that can be delivered step by step and verified against the source material. Collapsing multiple steps into one generation, stitching clips together, or filling in missing steps can undermine product accuracy and introduce unconfirmed torque values, tools, or warnings. assembly-one-step-clip is built for this constrained input: ordered stills plus seller-provided step facts, with one independent short clip per step and no concat.

How It Works

The skill narrows the inputs to at least one still visible to the host agent and arranged in step order, plus seller-supplied facts about parts, actions, or sequence numbers. The workflow includes:
- Frame review: record MIME type, width, height, aspect ratio, byte size, and alpha channel presence;
- Planning: write an annotated one-step-one-clip plan using only seller facts and visible image content; the plan is visible output, not approval;
- Validation: call beatra.models.list to confirm image-to-video support without driving_audio, then check pricing and constraints;
- Confirmation and generation: show a six-field card before each paid call, wait for user confirmation, then submit beatra.videos.animate through scripts/mcp_client.py and poll to terminal state.

By default, each still uses one call with an integer duration between 2 and 15 seconds; if the user does not choose, it defaults to 5 seconds. Results must be checked against step identity, motion, retained detail, actual size, duration, and billing.

Boundaries and Notes

It is intended for authorized assembly step photos only, not for inventing missing steps from public posts. If hard inputs are missing, ask only for the missing inputs; do not fabricate steps, specifications, or tools. Receiving files does not imply consent to use the stills beyond that step. On insufficient balance, keep the official top-up link and do not retry until the user confirms. Remote operations use the bundled MCP client only, not REST/OpenAPI fallback.