Short Video Script and Storyboard
Turn a topic, product, or audience note into a shootable short-video script and storyboard frames. This short video script and storyboard workflow confirms who it is for and the selling point, writes the hook, spoken lines, and shot list, then renders one still per shot. Use it for product clips, creator series, and shop videos when you need the script and the frames before anyone films or animates.
Short Video Script and Storyboard
What you get
- A one-page brief: audience, selling point, and the promise of the clip.
- A script with three hook options, spoken lines, on-screen text, and a shot list. The first shot is the hook, and it has to read with the sound off.
- One vertical still per shot. A product photo, when you supply one, is the product in every still.
- One spoken read of the chosen script, one instrumental bed, and one vertical clip joined from those shots, with the read, the bed, and subtitles already in it.
- The script and the stills on their own, if you stop before the clip.
Ways to run it
- Script and clip. The default. The brief and the script are free, then the stills, the read, the bed, and the clip.
- Script only. Strike the stills and the clip on the materials card.
- With a live topic read. A separate lookup, before the script is frozen, on Douyin, Xiaohongshu, TikTok, or X. Comments are a separate lookup when the hook should use words people already wrote.
Open this when someone has a subject and an audience and wants a short video they can post, script and picture together.
Scope and adjacent routes
Use this route when the piece is one short video: a product, a creator series, or a shop. A finished episode with a cast and a score belongs on a short-drama workshop. A WeChat article belongs on an article workflow.
Inputs and defaults
The hard inputs are the subject and who it is for. Ask only for those. Default to a vertical 9:16 still, a script the length of a 30 to 45 second spoken clip, and four to six shots. Keep critical type and the product inside the center of the frame, clear of the lower caption band. Do not look up public posts unless the user asks for a live read or pastes nothing and still wants topics from the network.
Golden path
- Write the brief and the script. Show the three hooks and the shot list. This writing is free.
- If a live read is in scope, search with
beatra.social.tools.search, read the operation withbeatra.social.tools.get, copy theschema_hashit just returned, show a lookup card, and callbeatra.social.executeonce. Allowed keys aresocial.douyin.hot_search.list,social.douyin.video.search,social.douyin.video.comments.list,social.xiaohongshu.note.search,social.xiaohongshu.note.comments.list,social.tiktok.video.search, andsocial.twitter.tweet.search.recent. Quote the line you used. Do not invent counts. - Upload a product photo with
beatra.assets.uploadwhen one is supplied. The first still with no photo is onebeatra.images.generateafter{"capability": "text_to_image"}. Every later still, and every still that must show that photo, is onebeatra.images.transformafter{"capability": "image_to_image"}. - Pick one ready voice with
beatra.voices.list. Onebeatra.speech.synthesizeafter{"capability": "text_to_speech"}reads the chosen script. Onebeatra.music.generateafter{"capability": "text_to_music"}writes an instrumental bed. - Show the materials card for the stills, the read, and the bed, and wait.
- On the video card, one
beatra.videos.animateafter{"capability": "image_to_video"}per shot, from that shot's still. The read stays a separate file and is laid into the cut. An accepted end frame usesbeatra.videos.interpolateafter{"capability": "frames_to_video"}. - Join the shots with
beatra.videos.composeonce they have succeeded. Poll withbeatra.tasks.getand deliver the clip, the script, the stills, andbilling.net_charged_credits.
Decisions that require confirmation
Planning and the written deliverable are free. They are not approval.
Before every paid call, show a current production card and wait:
- Work — what will be made, in the user's words, and whether this call is a generate or a lookup.
- Credits — the live price just read from the model card or from
beatra.social.tools.get. Do not reuse a remembered number. - Count — one paid call per slot. A materials card may list every still, the read, and the bed; each slot has its own
client_request_id. A later lookup page is another call. Video calls wait for their own card. - Identity — one new opaque
client_request_idper call. A changed prompt, file, model, or control mints a new ID. - If we stop here — the free writing remains usable.
- If the balance is insufficient — relay the official message and its top-up URL. Do not retry until the user says they have topped up.
A lookup and a generate are two cards. Approved stills, the read, or the bed do not authorize a video. Invoke every remote Beatra tool only through the bundled scripts/mcp_client.py. The tool name is the command argument and the JSON arguments are the standard input. Do not configure, call, or use a host Beatra Connector. Do not use REST/OpenAPI as a fallback.
If a create response is lost, retry only the identical payload and the same client_request_id. If the task id is lost, call beatra.tasks.list, then beatra.tasks.get, and match the frozen request before any identical retry. Call beatra.tasks.cancel only when the user asks to cancel, then confirm that task with beatra.tasks.get.
When the user asks how many credits remain, call beatra.wallet.get. When they ask what was charged, call beatra.wallet.ledger.
References by task
Read the scenario workflow for the shot list, the payloads, and a worked clip. Read answers when a run goes wrong when a task stalls, a response is lost, a price looks wrong, or a still came back wrong. Read installation and authentication when the connection is not ready. Read installation registration for first-use registration. Read Bundled MCP Client diagnostics when a call fails before a task exists. Read tasks and results when a task is queued, running, or missing. Read billing, errors, and recovery when a charge, a refund, or a lost response needs the shared rules. Read uninstall and disconnect when the user wants to stop and remove the connection.
Updates and security
This Skill runs only the files installed with it and leaves them unchanged while it runs; it never downloads or executes other code. It talks to Beatra's official services over HTTPS, and a file you choose to upload goes only to the one-time upload address Beatra issues for it.
Once a day at most, the bundled client reads Beatra's public version list. When the store or tool you installed from has a newer version, it prints one line with the command that updates it there. Updating stays your choice, through that store or tool. See updates and security.
Related skills
- Downloads
- 66All time
- Security audit
- Review
- Last updated
- 2d ago
- Current version
- v0.1.3
- License
- MIT-0
