AI vertical shorts are vertical videos for TikTok, Reels or YouTube Shorts that an AI agent helps write, narrate, animate and render. shorts-kit is an open source kit that turns a coding agent into that studio: agent skills, 20+ story flows, a fact ledger and CC0 SFX, rendered with Remotion. You install it in a repo, prompt the agent, and get a rendered file.
you + coding agent (Claude Code, Codex, Cursor)
|
v
[ shorts-kit repo ]
+-- agent skills (9+)
+-- story flows (20+)
+-- fact ledger
+-- CC0 SFX library
|
v
Remotion render (vertical 9:16 MP4)
|
+--> Creator OS: posts:create --platforms
tiktok,youtube,instagram
|
+--> analytics:posts, then adjust
What Is an AI Vertical Shorts Studio? (shorts-kit Explained)
A shorts studio is everything between an idea and a finished vertical MP4, and shorts-kit puts that pipeline inside a repo your coding agent can read.
The source project is howznguyen/shorts-kit, described as a way to make narrated vertical shorts for TikTok, YouTube Shorts and Reels with a coding agent and Remotion. It ships 9+ agent skills, 20+ story flows, a fact ledger and CC0 SFX. Remotion is the React based video framework that does the actual frame rendering.
That combination matters because the hard part of short form is not the editing. It is the repetition. You need a hook that survives the first three seconds, a script that does not invent facts, a voice track, captions that stay readable on a phone, sound effects that will not get the video muted, and a render that comes out at the right aspect ratio every time. A studio is the thing that makes that repeatable instead of heroic.
Creator OS does not build that studio and this post is not a feature announcement for it. shorts-kit is a separate open source project. What Creator OS gives you is the other end: somewhere to publish the finished clips to TikTok, Reels and YouTube Shorts from the same agent session, and analytics that tell you whether the clip actually held attention.
How shorts-kit Turns a Coding Agent Into a Shorts Studio
A coding agent with repo access can already run terminal commands and edit files, so shorts-kit teaches it the parts it does not know: how a short is structured, where assets live, and which scripts to call.
The workflow looks like this. You clone the repo, open it in Claude Code, Codex, Cursor or any agent that can read files and run commands, and then you prompt in plain language. The skills tell the agent which folders hold story flows and sound effects, how to write a flow file, and how to trigger a Remotion render. You review the output as files, not as a chat message.
This is the same pattern as the agent skills approach to social media automation: the model supplies judgment, the repo supplies the procedure. The difference is that here the deliverable is a media file rather than a post.
If you have not set up a coding agent before, the Claude Code walkthrough covers the basics of pointing one at a working directory, and the Codex post covers the same idea from the OpenAI side. Watch the walkthroughs on the KevBuildsApps YouTube channel if you prefer to see a session run end to end.
What Are Agent Skills and 20+ Story Flows?
Skills are the instructions. Story flows are the reusable formats. Together they are why the agent can produce a fifth short in ten minutes instead of starting from a blank page.
| Piece | What it is | What you do with it |
|---|---|---|
| Agent skill | A file the coding agent reads that describes one job, such as writing a script or rendering a video | Nothing directly. You prompt, the agent loads the skill |
| Story flow | A repeatable narrative shape for a short, with beats and timing | Pick one, or copy one and rewrite it for your niche |
| Fact ledger | A record of the claims in a script and where each came from | Check it before render, or have the agent check it |
| SFX library | CC0 sound effects | Reference them in a flow instead of hunting for audio |
A story flow is the structure and not the script. Something like a myth and correction shape, or a three item list with a payoff, gives the agent a skeleton: hook in the first two seconds, one idea per beat, a button at the end. Because the flow lives in the repo, you can edit it. Once a format works for your audience, you copy the flow, change the wording rules, and now every future short in that series sounds like you.
Twenty plus flows across 9 plus skills is a lot of surface area. Start with one flow in your own niche and run it three times before you touch the rest. The people who get value from a kit like this are the ones who treat it as a template shelf, not a slot machine.
How to Install shorts-kit and Render Your First Narrated Short
The fastest path is to let the agent do the install and then give it one narrow brief.
- Clone the shorts-kit repo from GitHub into a working directory.
- Install dependencies and let the agent read the repo’s own README for the exact commands. Do not guess at package names.
- Ask the agent to list the available story flows and skills before you write anything.
- Pick one flow. Give the agent a topic, an audience and a promise, in one paragraph.
- Ask for the script first, with the fact ledger filled in, before any render.
- Read the script out loud. If it does not sound like speech, send it back.
- Then ask for the render. Remotion produces the vertical file.
A first prompt that works:
List the story flows in this repo, then pick the one
best suited to a 40 second explainer for freelance
designers. Write the script only. Fill the fact
ledger for every claim. Do not render yet.
The pause after the script is the most useful habit in the whole pipeline. Renders take time and cost nothing to avoid. A bad script that you catch in text form costs you thirty seconds. The same script discovered after a render costs you the render plus your attention.
For the publishing half, the YouTube Shorts automation post shows how the finished file gets to the channel.
How the Fact Ledger Keeps Your AI Shorts Accurate
A fact ledger makes the agent show its sources before the video exists, which is the cheapest place to catch an invented number.
Language models produce confident specifics. A short that states a statistic, a date or a price that turns out to be wrong is worse than a short with no statistic, because it travels. The ledger forces a column of provenance next to every claim. When the agent cannot cite a source, the claim gets cut or softened. You can also ask for a version with all unverifiable claims removed and compare the two scripts side by side.
This connects to something Creator OS already does. If your shorts are based on your own published writing, the workflow in letting an AI agent research your published articles gives the agent a known source set to cite from, so the ledger fills itself from your own pages rather than from memory.
Two rules keep the ledger honest. First, a claim without a source does not ship. Second, the source has to be something you could open and read, not a vibe. An agent that can quote your own article back to you is an agent you can check.
How to Use CC0 SFX and Remotion Templates Without Copyright Strikes
CC0 sound effects are the safest audio you can put in a short, because the rights holder has waived the rights, but the license is only one part of staying clean.
Keep three habits:
- Track every asset in the repo. If a sound file came from the shorts-kit library, leave it where the kit put it so the provenance is obvious later.
- Do not swap in audio you found elsewhere. The moment you drop a track from a random download folder into a flow, you have left the safe zone. Music is where most claims come from, and the kit’s SFX are effects, not a music library.
- Bake the audio into the render. A finished file with the sound already inside is easier to publish and easier to audit than a project that assembles audio at upload time.
The same logic applies on the platform side. Instagram, for example, does not let the API attach trending audio, so sound has to be in the file. If you are posting Reels through an agent, read how to let an AI agent post to Instagram before you plan your audio workflow.
How to Mass-Produce Shorts for TikTok, Reels, and YouTube Shorts
Mass production works when the variable parts are content and the fixed parts are format, so you change the topic each time and never the structure.
A batch loop that holds up:
- Write ten topics in a spreadsheet, one line each.
- Run flow one across all ten, script only, ledger filled.
- Read all ten scripts in one sitting and cut the weak ones. Six surviving scripts is a good day.
- Render the survivors in one agent session.
- Publish them, then read the numbers.
The temptation is to automate steps one through four and skip step five. Do not. A batch of twelve shorts with no feedback loop is twelve guesses.
For the publish step, Creator OS takes the same command shape across networks. Upload the file once, get a media id back, then reference it:
creatoros media:upload ./out/short-014.mp4
creatoros posts:create \
--text "Three pricing mistakes freelance designers make" \
--platforms tiktok,youtube,instagram \
--media med_abc123 \
--title "Pricing mistakes" \
--scheduledAt 2026-03-04T18:00:00Z \
--timezone America/Toronto
One media id, three networks, one scheduled slot. Networks you listed but have not connected come back in missing_platforms and the rest still go out, so a missing TikTok connection does not block the Reel.
Then measure. creatoros analytics:posts returns per post numbers across connected platforms, and for Instagram Reels it includes watch time fields that tell you whether people stayed. If a batch of shorts all lose viewers in the first three seconds, the hook is the problem, not the render.
Can an AI Social Agent Also Publish the Clips It Makes?
Yes, if the agent that renders the short can also reach a publishing API, the loop from idea to published clip closes inside one session.
Creator OS ships a hosted MCP server and a CLI so an agent can run your accounts. The MCP server lives at https://mcp.creatoros.ca/mcp with nothing to install, and the tool names include create_post, upload_media_from_url and get_post_analytics. A read only connection only sees read tools and the API refuses writes from it, so you can give a research agent visibility without giving it the keys to publish.
The open source Social Agents harness at kevinbadi/social-agents goes further: it interviews you about your brand, then posts, replies to comments and DMs, runs automations and reports, with a local dashboard and your own model. An agent that makes shorts and an agent that runs the accounts can be the same agent, or two agents sharing one workspace key. The Chrome relay post covers the browser side if your workflow lives in a tab.
For the human side of the loop, the launch video walks through what Creator OS does and how the pieces fit.
FAQ
What is shorts-kit and does it need a coding agent?
shorts-kit is an open source kit from howznguyen for making narrated vertical shorts with a coding agent and Remotion. It needs a coding agent, because the agent is what reads the skills, writes the story flow output and runs the render commands. A general chat assistant without file and terminal access cannot drive it.
How many story flows and agent skills does shorts-kit include?
The project lists 9+ agent skills and 20+ story flows, plus a fact ledger and a CC0 SFX library. The counts matter less than the structure: each flow is a reusable shape you can copy and rewrite. Check the repo for the current list rather than trusting a number in a blog post.
Can I mass-produce TikTok and Reels shorts with an AI social agent?
You can, if the production step and the publishing step both run through something the agent can call. shorts-kit renders the file, and Creator OS publishes it to TikTok, Instagram Reels and YouTube Shorts from a CLI or the MCP server, with one media upload reused across networks. Keep a human review pass on the scripts and on the analytics.
What is a fact ledger in AI shorts production?
A fact ledger is a record of each claim in a script next to the source for it. It gives you a place to reject unsourced numbers before a render instead of after a comment section. Ask the agent to fill the ledger before it renders anything.
Are the SFX in shorts-kit CC0 and safe for monetization?
The project describes its sound effects as CC0, which means the rights holder has waived the rights, and CC0 audio is generally the safest choice for monetized video. Read the repo’s own license notes yourself, and keep your own record of which files you used in which short. Music is a separate question from effects, so do not assume a track from elsewhere is covered.
Get Started With Creator OS
Build the clips wherever you like, then publish and measure them in one place. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included. Start at https://www.creatoros.ca/sign-up, and read the setup docs at https://www.creatoros.ca/docs.
Get started for $0
Free trial for new subscribers. Cancel anytime.