← ClaudeAtlas

video-repurposerlisted

Turn a long recording (Zoom masterclass, webinar, cohort session, screen-share teaching video) into standalone LinkedIn clips - transcribe with Deepgram, choose the cuts, QC and score them, show a review table for approval, then render finished captioned MP4s with ffmpeg and emit tracker-sheet rows. Use this whenever the user drops a video file or recording and wants clips, or says any of "clip this", "repurpose this recording", "cut this into clips", "make LinkedIn videos from this", "which parts of this are worth posting", "score these clips", or asks to update the Zoom Video Clips tracker or add Drive links to it. Use it even when they only hand over a video path with little explanation - a long recording plus any mention of clips, posting, or LinkedIn is this skill.
rajesh-ezio/clipsy · ★ 0 · Code & Development · score 67
Install: claude install-skill rajesh-ezio/clipsy
# Video repurposer Long recording in, publishable standalone clips out. **You decide what to publish and exactly where to cut. ffmpeg renders finished files. The user uploads and posts.** Holding that line is what keeps this reliable — the editorial judgment is the hard part and the only part that needs you. ## Division of labour — the user does these, not you | You | The user, manually | |---|---| | Transcribe, choose cuts, QC, score | Approves the review table | | Render the finished MP4s | Watches them; asks for a cut to be adjusted if one needs it | | Read Drive links back, emit the TSV | Uploads to Drive, pastes the TSV, posts | One settled constraint, not a gap to fix: the Google Drive connector is **file-level only — it cannot write spreadsheet cells**, so rows are emitted as TSV for the user to paste. Don't relitigate it mid-run. ## Setup **First, check the machine.** It takes a second and names the exact fix for anything missing (ffmpeg, the Deepgram key, fonts). Run it at the start of every job; on a new machine it is the difference between a clean run and a failure at step 2 or step 6: ```bash python3 ~/.claude/skills/video-repurposer/scripts/check_setup.py ``` If it reports a missing Deepgram key, ask the user to create the key file themselves with the command it prints. Never ask for the key in chat, and never write it anywhere inside this skill folder. The folder is a git repo, and part of it is public. Scripts live in this skill and run from anywhere.