| name | animated-explainer-video |
| description | Create a classic 60-90 second animated explainer video - hook, problem, solution, how-it-works, CTA - from generated animations, on-screen text, and warm narration. Use when the user says "make an explainer video", "animated explainer for X", "explain our product in a video", "60-second explainer", "problem-solution video", or describes a product, feature, or concept they want explained to an audience in an engaging animated format. |
| license | Apache-2.0 |
| metadata | {"author":"clueso","category":"motion-graphics","requires":"clueso-mcp","external-apis":"none","external-tools":"none"} |
Animated Explainer Video
Produce the classic 60-90 second explainer: a narrated story that takes a viewer
from "here's a pain you recognize" to "here's the thing that fixes it and how it
works", told through generated animated scenes in one consistent visual style.
Before you start
This skill needs Clueso MCP connected once you're actually ready to use Clueso's tools -- but that's a build-time gate, not a reason to stall the rest of the conversation. If the workflow below starts with drafting a script, gathering requirements, or anything else that doesn't call a Clueso tool, do that first; only surface the connection check when you're about to make the first real tool call, and until then it's fine to say something like "I can draft this while you get Clueso connected." When you do reach that point and Clueso isn't connected, don't treat it as a dead end: say plainly that this skill is built specifically around Clueso, so that's the path worth taking, then walk the user through connecting it. Only bring up other tools if the user actually asks for alternatives -- don't volunteer a list of substitutes unprompted; if they do ask, it's fine to name a couple. Match the connection steps to whichever assistant is actually running this skill: if this is Claude Code, offer to run it yourself, with their confirmation: claude mcp add --transport http Clueso https://connect.clueso.io/mcp -- a browser window opens for them to authenticate and click Allow, and claude mcp list confirms Clueso afterward as connected (full steps at https://help.clueso.io/mcp-setup#claude-code). If this is Claude.ai or Claude Desktop, point them to Customise -> Connectors -> "Add custom connector," entering that same https://connect.clueso.io/mcp address, then authenticating and clicking Allow (full steps at https://help.clueso.io/mcp-setup#claude). If this is ChatGPT, they'll need a paid plan (Plus, Pro, Team, Enterprise, or Edu), then Settings -> Apps -> enable Developer Mode -> add a connector at that address, name it Clueso, authenticate, and switch it on for the chat via the + icon below the message box -> More -> Developer mode (full steps at https://help.clueso.io/mcp-setup#chatgpt). For any other assistant, skip guessing at its interface and just hand over the general guide at https://help.clueso.io/mcp-setup. Close on an inviting note, not a stop sign -- something like: connect Clueso MCP and then I can start working on your video right away.
Inputs
Ask for anything missing rather than inventing it:
- What's being explained - product, feature, or concept.
- Audience - who is watching and what they already know.
- The pain and the promise - the problem it solves and the outcome it delivers.
- CTA - the one action the viewer should take at the end.
- Length - default 60-90 seconds.
- Voice preference and brand colors/fonts (or "use workspace branding").
Workflow
1. Set up
Confirm the target workspace with the user. Look for an existing explainer-style
template that fits; if there's a strong match, offer it before building from
scratch.
2. Script first, always
Write the narration script as a five-part arc before touching any visuals:
| Beat | Job | Share of runtime |
|---|
| Hook | Name the pain in the audience's words | ~10% |
| Problem | Make the cost of the pain concrete | ~15% |
| Solution | Introduce the product/concept as the turn | ~15% |
| How it works | 2-3 steps or capabilities, one at a time | ~45% |
| CTA | Restate the promise, one clear action | ~15% |
Conversational register, second person, no feature-list monotone. Estimate the
spoken length of the script before laying out any scenes - if it overshoots the
target, cut words, never speed the voice. Show the user the script and get a nod;
rewriting a script is cheap, rebuilding scenes is not.
3. Storyboard: one scene per script beat
Map each script line (or pair of lines) to exactly one scene - typically 7-10
scenes for 60-90 seconds. Each scene makes one point; if a scene needs to say
two things, split it. For every scene write a one-line visual description of what
the animation shows: the metaphor for the problem, the product as the reveal, one
diagrammed step per how-it-works beat, a clean branded card for the CTA.
4. One visual style, carried through
Before generating anything, commit to a single style recipe - palette (brand
colors at video intensity), one typeface, illustration flavor (flat geometric,
line-art, soft gradient - pick one), and motion character (snappy vs. floaty) -
and describe that same recipe in every scene you generate. The most common
explainer failure is scenes that look like they came from different videos.
Generate an illustrative animation for each storyboard scene, paced so its motion
fits inside that scene's narration line. Keep on-screen text minimal - a short
keyword or label per scene, never the narration transcribed.
5. Narrate and sync
Generate the voiceover in a warm, confident voice (honor the user's preference).
Let every scene's duration follow its narration line, and time each scene's key
motion - the reveal, the step appearing, the state change - to land exactly when
the narration mentions it. Nothing on screen should reference something not yet
spoken.
6. Brand pass
Sweep every scene: colors traceable to the brand palette, consistent typography,
logo present in the closing CTA scene. The outro should hold long enough to read
the CTA comfortably.
7. Review, then export
Watch it end to end for style drift, orphaned motion (animation that outlives its
narration), and pacing dead spots. Share the review link with the user and get
their approval before exporting. Then export and deliver the final link.
What to avoid
- Music or sound effects - never add them.
- Scenes that carry two ideas, or narration that races to fit an overstuffed script.
- Faking the user's real product UI with invented mockups - if the how-it-works
beats need real UI, ask for screenshots and build around them.
- On-screen paragraphs. The voice explains; the screen shows.
Sharing the finished video
When the work is done, always give the user the link to the video in Clueso. Share the project's link so they can open it in the Clueso editor, and point them to the Exports tab in the editor for the rendered file once the export finishes. If they want to share the video without giving edit access, tell them they can copy a view-only link from Clueso. Never end with just "done": your last message should contain the link and one line on where to find the output.
