skills/video-podcast-producer/SKILL.md
End-to-end video/podcast post-production pipeline: split recordings into topic-based clips, remove dead time, generate thumbnails (landscape 16:9 and vertical 9:16), create YouTube metadata (titles, descriptions, tags), and cut Shorts. Use when the user has a video or audio recording (meeting, podcast, interview, webinar, stream) and wants to process it for publishing on YouTube, social media, or any platform. Triggers: 'cut this recording', 'make YouTube clips', 'create thumbnails', 'process this meeting recording', 'split into episodes', 'make shorts from this video', 'publish this recording'.
npx skillsauth add razbakov/skills video-podcast-producerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transform raw video/audio recordings into publish-ready content: trimmed, split by topic, with thumbnails and YouTube metadata. Uses ffmpeg for video processing and the brand-poster skill for professional thumbnails.
Use the transcribe-via-faster-whisper skill to transcribe the recording. This produces transcription.json (timestamped segments) and transcription.txt (full text).
Review timestamped segments to identify:
Present a cut plan table to the user: | # | Title idea | Time range | Duration | |---|-----------|------------|----------|
Wait for user approval before cutting.
Use ffmpeg stream copy for speed (no re-encoding):
# Single segment
ffmpeg -y -i "$SRC" -ss START -to END -c copy output.mp4
# Multi-part clip (skip dead time within a topic)
ffmpeg -y -i "$SRC" -ss START1 -to END1 -c copy /tmp/partA.mp4
ffmpeg -y -i "$SRC" -ss START2 -to END2 -c copy /tmp/partB.mp4
echo "file '/tmp/partA.mp4'
file '/tmp/partB.mp4'" > /tmp/concat.txt
ffmpeg -y -f concat -safe 0 -i /tmp/concat.txt -c copy output.mp4
Run independent cuts in parallel with & and wait.
For each clip, pick the most engaging 50-70 second moment. Crop center and scale to 1080x1920:
ffmpeg -y -ss START -to END -i "$SRC" \
-vf "crop=405:720:437:0,scale=1080:1920" \
-c:v libx264 -crf 23 -c:a aac output-short.mp4
The crop values assume 1280x720 source. Adjust for other resolutions:
Use the brand-poster skill to generate thumbnails for each clip.
For each clip, generate two thumbnails:
Design principles:
For each clip, generate:
Save all metadata in a single youtube-metadata.md file.
Structure output in a dated meeting/episode folder:
meetings/YYYY-MM-DD/
├── transcription.txt # Full text
├── transcription.json # Timestamped segments
├── 01-clip-name.mp4 # Topic clips (16:9)
├── 01-thumbnail.png # Landscape thumbnail (1280x720)
├── 01-short.mp4 # Vertical short (9:16)
├── 01-short-thumb.png # Vertical thumbnail (1080x1920)
├── ...
├── youtube-metadata.md # Titles, descriptions, tags
└── cuts.txt # Cut plan documentation
Use Claude in Chrome (MCP browser extension) to automate YouTube Studio uploads:
https://studio.youtube.comImportant limitations:
<input type="file"> elements — user must do this manuallyAfter publishing:
brand-poster skill for consistency.-c copy) for speed when cutting — only re-encode for crops (Shorts).development
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
testing
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
development
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
development
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.