skills/youtube-metadata-updater/SKILL.md
Download a YouTube video, transcribe it, generate optimized title/description/chapters/tags, create a thumbnail, and update the video via YouTube Data API. Use when the user shares a YouTube URL and wants title, description, chapters, tags, or thumbnail updated. Triggers: 'update youtube', 'need title and description', 'add chapters', 'fix youtube metadata', 'generate thumbnail for youtube', or when user shares a youtube.com/watch URL and asks for metadata.
npx skillsauth add razbakov/skills youtube-metadata-updaterInstall 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.
Given a YouTube video URL, produce and apply optimized metadata: title, description with chapters, tags, and a thumbnail.
yt-dlp (audio download)localhost:8000 (transcription)~/.config/youtube/token.json (created on first run)~/Projects/ikigai/.bin/youtube-update.py# Extract video ID from URL (the ?v= parameter)
VIDEO_ID="HOzfntvOXMY"
MEETING_DIR="<project>/meetings/YYYY-MM-DD"
mkdir -p "$MEETING_DIR"
uvx yt-dlp -f "bestaudio" -o "$MEETING_DIR/livestream.%(ext)s" \
"https://www.youtube.com/watch?v=$VIDEO_ID"
Also fetch existing metadata for context:
uvx yt-dlp --dump-json --no-download "https://www.youtube.com/watch?v=$VIDEO_ID" | \
python3 -c "import json,sys; d=json.load(sys.stdin); print('Title:', d.get('title')); print('Duration:', d.get('duration_string')); print('Channel:', d.get('channel'))"
The faster-whisper server crashes on large files. Split into 2-minute chunks and transcribe sequentially using the small model.
# Split into 2-min m4a chunks (copy codec, fast)
DURATION=$(ffprobe -v error -show_entries format=duration -of csv=p=0 "$MEETING_DIR/livestream.m4a" | cut -d. -f1)
CHUNK=120
for i in $(seq 0 $CHUNK $((DURATION - 1))); do
idx=$(printf "%02d" $((i / CHUNK)))
ffmpeg -i "$MEETING_DIR/livestream.m4a" -ss $i -t $CHUNK -c copy "/tmp/mchunk_${idx}.m4a" -y
done
Transcribe all chunks with offset correction:
# Use Systran/faster-whisper-small (not large-v3, crashes on CPU)
# Add chunk offset to each segment's start time
# Save combined result to $MEETING_DIR/transcription.txt
# Format: [M:SS] text
Key lessons:
Systran/faster-whisper-large-v3 crashes after 1-2 chunks on CPU — use smallRead the full transcript. Identify:
Output format — save to $MEETING_DIR/youtube-metadata.md:
# YouTube Metadata — [Series] Meeting #N (YYYY-MM-DD)
**Title:** [Clickable title under 70 chars]
**Description:**
[2-3 sentence summary]
[Series context line]
Chapters:
0:00 [First chapter]
...
[Links section]
#tag1 #tag2 ...
**Tags:** tag1, tag2, ...
Also save $MEETING_DIR/youtube-update.json for the API:
{
"title": "...",
"description": "...",
"tags": ["..."],
"categoryId": "28"
}
Category IDs: 22=People & Blogs, 27=Education, 28=Science & Technology.
Create an HTML file ($MEETING_DIR/thumbnail.html) at 1280x720px with:
Capture at 2x resolution:
google-chrome --headless --screenshot="$MEETING_DIR/thumbnail.png" \
--window-size=1280,720 --force-device-scale-factor=2 \
"$MEETING_DIR/thumbnail.html"
Show the thumbnail to the user for approval before uploading.
uvx --from google-api-python-client --with google-auth-oauthlib --with google-auth-httplib2 \
python3 ~/Projects/ikigai/.bin/youtube-update.py $VIDEO_ID \
--meta "$MEETING_DIR/youtube-update.json" \
--thumbnail "$MEETING_DIR/thumbnail.png"
First run requires OAuth browser authorization. Token is cached at ~/.config/youtube/token.json.
If YouTube Data API is not enabled, direct user to:
https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=PROJECT_ID
Verify the update by showing the video URL and confirming the title was applied.
| File | Purpose |
|------|---------|
| livestream.m4a | Downloaded audio |
| transcription.txt | Timestamped transcript |
| youtube-metadata.md | Human-readable metadata reference |
| youtube-update.json | API payload |
| thumbnail.html | Thumbnail source |
| thumbnail.png | Uploaded thumbnail |
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.