storyboard-generator_skill

Overview

This skill turns a user's story sketch into a polished storyboard sequence and batch-generates consistent storyboard illustrations. It refines the narrative, splits it into 6–10 storyboard panels with shot directions, and produces cohesive images in one of eight selectable visual styles. Generated images are saved to an Obsidian images folder and can be iterated on per-frame.

How this skill works

The skill first polishes the submitted story and extracts a concise story summary and emotional arc, then breaks the story into 6–10 panels with scene title, shot type, description, mood, and on-screen text. After confirming the panel script, it recommends 1–2 visual styles suited to the story, builds per-panel image prompts (style prefix, camera instruction, scene description, emotion, and an IMPORTANT consistency anchor), and invokes the Gemini image API to generate each frame. Images are saved to a dated Obsidian directory with consistent naming and resolution settings.

When to use it

• You have a story outline and need a clear storyboard for production or pitching.
• You want a quick set of cohesive concept images for a short film, animation, or comic.
• You need style-consistent visuals for story pacing reviews or client presentations.
• You want to iterate a single panel or re-generate failed frames without remaking the whole set.
• You prefer automatic saving into an Obsidian image folder for easy project organization.

Best practices

• Provide a clear prose description or bullet outline including main beats and key visual traits (character looks, locations, time of day).
• Confirm or adjust the 6–10-panel split before generation to control pacing and content.
• Select 1–2 recommended styles based on story tone; specify a preferred style to skip the recommendation step.
• Include explicit character appearance details to ensure visual consistency across panels (hair, costume, body type).
• Allow 2–3 second pauses between API calls to reduce rate-limit failures; review failure report and re-generate only failed frames.

Example use cases

• Turning a short prose scene into a 7-panel storyboard for a director’s pitch.
• Creating a 10-panel visual sequence in a Ghibli-watercolor style for a warm, coming-of-age short.
• Generating a cyberpunk concept storyboard for a game pitch with neon-lit cityscapes.
• Producing a black-and-white film-storyboard handoff for a commercial shoot.
• Iteratively refining a single problem frame after client feedback while keeping other panels unchanged.