You can turn a webinar into shorts with Claude, but not by running the same prompt you use for a YouTube video. A webinar is a different animal: slide-heavy, audio-variable, and built around a live audience. The recipe below treats it that way. You map chapters first, write chapter-level prompts, pull the Q&A and demo moments out separately, then batch the clips into a schedule you can run from Claude through Creator OS.
Webinar recording (60-90 min)
|
v
[1] Chapter map: timestamps + intent per block
|
v
[2] Chapter prompt -> candidate moments per block
|
v
[3] Split tracks: demo clips | Q&A clips | slide clips
|
v
[4] Edit pass (OPEN VIDEO EDIT skills, local render)
|
v
[5] Batch calendar JSON -> posts:bulk-upload --dryRun
|
v
[6] Schedule + first comment + analytics loopWhy Webinars Are Harder to Repurpose Than YouTube Videos
A YouTube video usually has one through-line. A webinar has a slide deck, a demo, a live Q&A, and a pitch, all in the same file. If you hand the whole recording to Claude and ask for shorts, you get clips that start mid-sentence, clips where the speaker is reading a slide the viewer cannot see, and clips that are really just a sales pitch with a hook bolted on.
That is why the original YouTube trick, covered in repurpose a long YouTube video into shorts with Claude, needs a webinar variant. The difference is the chapter map. Once Claude knows what each block of the webinar is trying to do, it stops guessing.
Map Your Webinar Chapters Before You Prompt Claude
Do this by hand, in a plain text file. It takes fifteen minutes and saves you an hour of bad clips. Write one line per block with a start timestamp, an end timestamp, and the intent.
WEBINAR: "Cold email that gets replies" (78 min)
00:00-06:40 intro + who this is for
06:40-19:10 the 3-part email structure (slide deck)
19:10-31:00 live demo: building an email in the tool
31:00-44:30 teardown of 4 real emails (slides)
44:30-58:00 live Q&A from chat
58:00-70:00 case walkthrough with numbers
70:00-78:00 offer + next steps
Two things you now know that a raw prompt would miss. The demo and the Q&A are structurally different from the slide sections, so they need different clip rules. And the last eight minutes are the offer, which should produce at most one clip, not five.
Write Chapter-Level Claude Prompts That Extract Clip-Worthy Moments
Do not prompt once for the whole file. Prompt once per chapter, and give Claude the intent of that chapter plus the clip rules that apply to it. Here is a prompt for the teardown block (31:00 to 44:30):
You are reviewing a webinar transcript section, 31:00 to 44:30.
Context: the speaker tears down 4 real cold emails on slides and
explains why each one failed.
Extract up to 4 clip candidates. For each, return:
- start and end timestamp (clip must be 20 to 50 seconds)
- the one sentence that works as an on-screen hook
- whether the moment depends on a slide being visible
Rules:
- Only pick moments where the point lands in audio alone.
- Skip anything that references "this slide" unless the speaker
reads the slide content out loud.
- No clip may start on a filler word.
That slide rule matters more than any other line in the prompt. When you get the results back, sort them into three buckets: audio-only (easy), slide-dependent (needs a screenshot or a zoom-in), and discard. Batch the easy ones first.
Run the same shape of prompt for the structure block, then a looser one for the intro. The intro often yields exactly one good clip: the “who this is for” line, which makes a strong opening short.
Turn Q&A and Demo Segments Into Standalone Shorts
Q&A clips have an advantage: they are already shaped like a short. One question, one answer, done. The trap is that the question is often in chat text, not in the audio. So ask Claude for the question and the answer as a pair:
Section: 44:30 to 58:00, live Q&A.
Return pairs: question (paraphrased into 1 line, max 90 chars),
answer timestamp range, and the single most quotable sentence.
Keep answers under 45 seconds. If the answer runs long, mark the
best 30-second window inside it and say what you cut.For the demo section, the clip needs a different treatment. A screen recording of someone clicking through a tool is hard to follow at shorts speed. Extract the demo moment, then speed up or trim the clicking so the result is the input and the output, not the mouse travel. If you want the editing side handled by agents rather than by hand, the open-source Claude video editor walkthrough and the OPEN VIDEO EDIT skills cover local renders with captions, counters and b-roll cards. The talking-head recipe in turn a talking head clip into an animated short with AI applies here too, since a webinar camera feed is usually a talking head with a screen share next to it.
Batch the Clips Into a Creator OS Scheduling Plan
Now you have a pile of files and timestamps. Do not schedule them one at a time in a web dashboard. Build one calendar file and upload it in a batch. Creator OS reads a JSON file for this:
creatoros posts:bulk-upload --file webinar-shorts.json --dryRun
The dry run is the point. It tells you what would publish before anything goes out. Fix the errors, then drop the flag.
Two CLI habits make the batch better. First, upload each clip once and reuse the media id across platforms, so you are not pushing the same file four times:
creatoros media:upload webinar-clip-03.mp4
Second, check captions against each platform’s limits before the batch, not after a failed post:
creatoros validate:post-length --text "Your hook line here #coldemail"
For schedule slots, ask Creator OS for the data rather than guessing:
creatoros analytics:best-time --platform instagram
creatoros analytics:best-time --platform youtube
Then spread the clips across two to three weeks. A 78-minute webinar should produce eight to fifteen shorts. If you post all of them in three days, you burn the whole asset in a weekend.
Handle Webinar-Specific Traps: Slides, Low Audio, and CTA Overload
Three problems show up in almost every webinar recording.
Slides. A clip where the speaker says “as you can see here” is dead on arrival. Either bake the slide into the frame as a still, or cut the reference. Claude can flag these moments for you when you put the rule in the prompt, as shown above.
Low audio. Webinar audio is often recorded from a headset mic with a room behind it. Trim silence and normalize before you upload. A clip that sounds quiet in the editor will sound worse on a phone speaker.
CTA overload. The offer section of a webinar is written for people who already sat through 70 minutes. A cold viewer has no context. Take at most one clip from the offer block, strip the urgency language, and give it a real hook. The rest of your shorts should teach something.
For the YouTube side specifically, remember that vertical clips under three minutes become Shorts automatically when you set them up properly. The details, including thumbnails and pinned first comments, are in YouTube scheduling for podcasters, which applies the same way to webinar recordings.
Publish and Schedule the Clips From Claude
This is where the recipe stops being a file-and-prompt exercise and starts running your accounts. Creator OS ships a hosted MCP server at https://mcp.creatoros.ca/mcp. You add it as a custom connector in Claude, sign in, pick the workspace, and choose read only or read and write. Nothing to install. Step-by-step setup lives at the MCP docs.
Once connected, you talk to your accounts in plain language:
Schedule webinar-clip-03 to Instagram Reels and YouTube Shorts
for Tuesday 9am Eastern. Caption from the file. Pin a first
comment with the link to the replay.
Under the hood Claude calls tools like create_post and get_best_time_to_post. It can also read back what happened with get_post_analytics and get_daily_metrics, and reply to comments with list_comments and reply_to_comment. Destructive tools are marked so Claude asks before deleting or disconnecting anything. Read-only connections can see read tools only, and the API refuses writes from them.
If you prefer a terminal, the CLI covers the same ground:
creatoros posts:create --text "The 3-part structure that got 41 replies" \
--platforms instagram,youtube --media webinar-clip-03.mp4 \
--scheduledAt 2025-06-10T09:00:00-04:00 --timezone America/New_York
Both paths respect each platform’s rules. YouTube clips get a title and a pinned first comment. Instagram Reels can take a custom cover. TikTok requires consent flags, which the simple post form fills for you. The full set of per-platform options is at the post options docs.
If you want an agent to handle the whole loop after the batch is scheduled, replying to comments and DMs and reporting back, Social Agents is an open-source harness that runs on Creator OS: npm start creatoros social-agents. It interviews you about your brand first, then works. You can see the whole thing running on the KevBuildsApps YouTube channel, and the launch video walks through the setup.
Get Started: Run the Recipe on Your Next Webinar
Here is the whole recipe in order, one line each.
- Write the chapter map by hand, with intent per block.
- Prompt Claude per chapter, with slide rules in the prompt.
- Pull Q&A as question-and-answer pairs, demo as input-to-output.
- Normalize audio, bake any needed slides, render with the editing skills.
- Build one JSON calendar, run
posts:bulk-upload --dryRun, fix, run again. - Connect the MCP server and let Claude schedule and confirm the slots.
- Check
analytics:best-timeandanalytics:postsafter week one, then shift the remaining clips.
If you shoot video as well as webinars, the motion workflow in GitHub motion maxxing is a good companion for the branding layer on top of these clips.
The Creator plan is $14.99/month or $59.99/year, with 11 platforms plus Skool, one account on each. API keys, the MCP server, the CLI and the agent skills are included in every plan. Start at https://www.creatoros.ca/sign-up, connect Claude, and run your next webinar through the recipe once. The second one gets faster.
Get started for $0
Free trial for new subscribers. Cancel anytime.