AI Comic Drama Shot Maker

The Specific Problem Solved

When producing AI comic dramas or motion comics, creators often need to convert static comic panels, character designs, or comic pages into dynamic shots. Manual keyframe drawing or traditional animation tools are inefficient and technically demanding, especially for serialized projects where maintaining consistency in character features and art style is challenging. This skill automates the process, directly transforming static visual assets into dynamic shots that adhere to comic visual language.

How the Skill Works

Core Capabilities

• Input Processing and Recognition: Accepts a shot event (character, action, scene, emotion, etc.) and at least one confirmed visual source (e.g., comic storyboard, character design). Automatically parses the source's MIME type, dimensions, art style, character features, clothing, scene, and emotion, recording these attributes.
• Intelligent Routing and Generation: Automatically selects a generation route based on input semantics. For example:
• For strict single storyboard or character images, routes to beatra.videos.animate for animation.
• For first-last storyboard transitions, routes to beatra.videos.interpolate for interpolation.
• For multiple loose references (e.g., character, style, scene references), routes to beatra.videos.generate_from_references.
• Without visual sources, first creates and confirms an original comic starting frame via beatra.images.generate, then animates it.
• Shot Card Construction and Freezing: Before calling, constructs a shot card including character features, clothing, art style, scene, action, emotion, camera, composition, and visible end state, and writes a positive prompt encoding action and atmosphere. Model defaults to auto unless specified by the user.
• Billing and State Management: Each shot is an independent paid stage. Before calling, shows the route, source images, prompt, model behavior, and estimate. Uses beatra.models.list to confirm model capabilities, polls task status via beatra.tasks.get until completion, and delivers video assets.

Key Workflow Steps

1. Source Material Review: Examines each visual source, records actual MIME type, width, height, aspect ratio, and byte size, identifying character features, clothing, art style, scene, action, emotion, camera, composition, and determined story beats.
2. Shot Card and Prompt Construction: Integrates all attributes to build the shot card and writes a positive prompt encoding action, atmosphere, and endpoint moment.
3. Route Selection and Calling: Selects the video tool (e.g., beatra.videos.animate) based on input semantics, calls beatra.models.list to confirm model matches actual media facts, then submits exactly one call.
4. Task Polling and Delivery: Records the returned task ID, polls via beatra.tasks.get until a terminal state, delivers video assets or links, and reports task status, model, dimensions, duration, and billing details.
5. Review and Continuity Check: Reviews results, checking facial features, clothing, art style, composition, action readability, and endpoint behavior to ensure character feature continuity across generated shots.

Applicable Boundaries and Notes

• Focus on Comic Visual Language: This skill is dedicated to comic, webcomic, guoman, anime, and illustration-style dynamic shots. Requests for human dramas or cinematic human dramas should route to the short drama workflow; storyboard or planning requests to the storyboard workflow; broad non-narrative video requests to the general video studio.
• Independent Billing Stages: Each shot is an independent paid video stage. Creating an original starting frame is an additional paid stage. Changing character features, art style, storyboard, references, prompts, model, aspect ratio, or video controls constitutes new logical paid work, requiring a new ID and confirmation.
• Task Recovery and Cancellation: If a response is lost, replay the exact frozen payload with the same stage ID. If a task ID is lost, use beatra.tasks.get to find candidate tasks and confirm. Only call beatra.tasks.cancel when requested by the user, and confirm the terminal state.
• Updates and Security: The skill automatically checks for updates every 24 hours but only replaces package files, not affecting existing installations. Silent checks can be disabled via --auto off.
• Non-Applicable Ranges: Does not handle non-comic visual language requests, does not configure the host Beatra Connector, and does not use REST/OpenAPI fallback.