← ClaudeAtlas

aie-video-webinar-publishlisted

BETA. Turn a recorded webinar into a publish-ready YouTube video — pull the recording off the webinar platform, strip the umms and ahs, cut the "can you hear me" cold open, build a thumbnail that still reads at 168px, write the title, description and chapters, and upload it private for review. Every stage verifies itself by re-measuring the output. Use this skill whenever someone says "edit the webinar recording," "publish last week's webinar," "take out the umms and ahs," "remove filler words from this video," "cut the dead air at the start," "put this on YouTube," "make a thumbnail for the video," or hands over a recording of a slides-plus-webcam session and asks to ship it. Works for any recording of that shape regardless of platform. Configure per channel in `webinar.config.md`.
mrhinkle/aienterprise-skills · ★ 2 · AI & Automation · score 68
Install: claude install-skill mrhinkle/aienterprise-skills
# Webinar → YouTube (BETA) > **Beta.** The editing and verification stages are proven on real hour-long > recordings. The upload stage assumes a Composio-connected YouTube account; if > yours is wired differently, stop after step 7 and upload by hand — everything > before that is platform-independent. One job: take an hour of raw webinar and produce something worth someone's click, without silently mangling the speech in the process. The reason this is not a two-line ffmpeg script is that **every stage here has a failure mode that produces a plausible-looking wrong result.** A cut list can look perfect and land on the wrong words. A render can be exactly the right duration and contain exactly the wrong audio. The only defence that worked was re-measuring the output instead of trusting the plan, so that is built into each step. Copy `reference/webinar.config.example.md` to `webinar.config.md` and fill in your channel, brand and platform details before the first run. Work in a per-webinar folder. ## Process ### 1. Get the recording Webinar platforms rarely expose recordings through their API even when they have one — `reference/platform-retrieval.md` covers where the file actually lives on the common hosts, and the traps (expired replay links, download buttons that are not in the API, config wizards that look like the right menu but aren't). Whatever the source: get an MP4 on disk, and check its duration against the session length the platform reports before going furt