Source: raw/How_to_Automate_Content_Creation_With_Claude_AI_Full_Workflow.md (auto-caption transcript)

Creator: AI Master (YouTube @iamAImaster) · URL: https://www.youtube.com/watch?v=JZ-XHoiyFqI · Published: not in the transcript · Sponsor: Riverside. The whole workflow runs on the sponsor’s connector, so confidence is low.

AI Master connects the Riverside connector to Claude and runs four content jobs from one chat: planning what to shoot from the back catalogue, transcript-led editing, cutting a captioned vertical clip, and scheduling. The pattern worth keeping is reasoning before cutting. Claude reads the transcript, says what it will remove and why, and leaves the edit in Riverside where the creator can listen back. The creator still checks every cut, because Claude “once changed its mind on the same clip 20 minutes apart.”

Key Takeaways

  • The connector gives Claude the archive and the tools. After you authorize Riverside, Claude can read past recordings and transcripts and operate Riverside’s editing, clipping and publishing tools. “On its own, Claude can’t analyze footage, let alone edit it.”
  • Plan from gaps in what you’ve made. Prompt: “Look through all my past videos on this channel. Tell me which topics I keep avoiding. Then, draft two weeks of shooting, eight videos in the order I should shoot them, one line each on why.” Some ideas came straight from real gaps. The generic AI-tool ideas “go straight in the bin.” For interview shows, ask which guests you promised to have back or keep almost booking.
  • Edit by transcript, and ask for the reasons. Prompt: “Review the transcript of the latest video. Remove any failed attempts to start a sentence and the section where I lose my train of thought. Let me know exactly what you removed and why.” Claude found the latest recording by itself, created a new “clean cut” edit, ran a disfluency pass, and made 72 cuts.
  • It knew what not to cut. A garbled stretch of transcript around 11 minutes was Riverside mis-transcribing the AI voice in a live demo. Claude kept the block and told the creator to listen back before publishing. “That’s the part that made me trust the rest of it.”
  • The automatic pass works at word level only. It catches stutters and doubled words, not a whole clause said twice. A follow-up prompt asking it to “cut out the repetition, the full lines I said twice” handled that. Listen to the timeline anyway, because “the transcript doesn’t capture intonation.”
  • Describe the clip moment in words. Prompt: “Create a viral vertical video 9:16 for me from this footage. Add simple large captions and start the video exactly at the moment I state the precise figure.” About 15 seconds later Claude returned a link to a finished vertical clip in the Riverside editor, captioned and framed on the speaker’s face. That was under a minute of active time against “a real chunk of an evening” by hand. “The work didn’t disappear, it moved” to choosing which moment deserves a clip.
  • Ask for the schedule plan before anything is set. Prompt: “Schedule the long video for Thursday morning, then post the clip next week at the best time for its platform. Show me the plan before you set anything.” Claude checked the export status first. It warned that YouTube was the only connected account, so the vertical clip would go out as a Short there, not to TikTok or Instagram. Its plan listed source edit, channel, slot and export status per asset, with drafted titles and descriptions. It left privacy blank on purpose and put the Short on a weekday afternoon away from the long video’s day.
  • Know the chat-side limits. An export that wasn’t marked ready to publish forced an extra export-then-publish render. Claude checked status once and said it would not keep polling. Once something is scheduled, changing or cancelling it has to happen in Riverside’s web app.
  • Volume decides whether it pays. One video a month makes this “overkill.” Weekly shooting is where the time savings get real, and the system gets more useful as the archive grows.

Try It

  1. Connect the content tool your recordings already live in (Riverside here) as a Claude connector, and check which publishing accounts are actually connected before you plan a schedule.
  2. Run the gap-finding prompt over your back catalogue and keep only the ideas that come from your own material.
  3. Always add “tell me exactly what you removed and why” to editing prompts. It turns a finished file into a list you can argue with.
  4. Follow the automatic disfluency pass with a repeated-lines pass, then listen to every cut on the timeline.
  5. Write clip requests as a moment, not a timestamp (“start exactly where I state the figure”), plus aspect ratio and caption style.
  6. End scheduling prompts with “show me the plan before you set anything,” and set privacy and titles yourself.

Implementation

Tool/Service: Riverside (recording and editing platform) connected to Claude as a connector.

Setup: Add the Riverside connector in Claude and authorize it on Riverside. Connect the social accounts you want to publish to inside Riverside, since Claude can only post to accounts already connected there.

Cost: Per the video, the connector is available on Riverside’s Grow plan and up. The sponsor code (caption reads “codemaster”/“Codem”, probably an AI Master code) gives 30 days of Grow free. No plan prices are stated.

Integration notes: Edits are created as new edits inside the Riverside project, so the original recording stays intact. Scheduled items can’t be changed or cancelled from chat.

Open Questions

  • Exact promo code and Grow plan price. The captions garble the code and give no price.
  • How “the best time for its platform” is chosen. Claude argued for its slot, but the data source behind it is not shown.
  • Inconsistency between runs. The creator saw Claude change its mind on the same clip 20 minutes apart. How often this happens is not measured.