.claude/skills/chrome-youtube/SKILL.md
# CHROME-YOUTUBE-UPLOAD SKILL **Skill Name**: chrome-youtube-upload **Version**: 1.0.0 **Trigger**: `/chrome-youtube`, "upload to youtube", "open youtube studio", "schedule youtube video" **Description**: Open YouTube Studio in Chrome to upload, schedule, or manage CCW demo and boardroom videos when the API quota is exhausted or OAuth setup is incomplete. --- ## SKILL PURPOSE Automate or assist YouTube video management for the CCW channel through the browser UI. This is the fallback path whe
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/chrome-youtubeInstall 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.
Skill Name: chrome-youtube-upload
Version: 1.0.0
Trigger: /chrome-youtube, "upload to youtube", "open youtube studio", "schedule youtube video"
Description: Open YouTube Studio in Chrome to upload, schedule, or manage CCW demo and boardroom videos when the API quota is exhausted or OAuth setup is incomplete.
Automate or assist YouTube video management for the CCW channel through the browser UI. This is the fallback path when python scripts/youtube_upload.py cannot run due to API quota limits or OAuth issues.
Trigger phrases:
/chrome-youtubemcp__Claude_in_Chrome__navigate: https://studio.youtube.com
Screenshot to confirm login and channel:
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
Confirm channel name matches CCW channel. If wrong account → stop and tell user.
Navigate to Settings → Channel → Advanced settings:
mcp__Claude_in_Chrome__navigate: https://studio.youtube.com/channel/settings/advanced
mcp__Claude_in_Chrome__get_page_text
Extract the Channel ID and confirm it matches UChN8nQFig73BoefyMBIsN-w.
If mismatch → report to user before proceeding.
mcp__Claude_in_Chrome__navigate: https://studio.youtube.com/channel/videos
mcp__Claude_in_Chrome__get_page_text
Extract video list:
| Title | Status | Visibility |
|------------------------------------|------------|-------------|
| CCW Demo - Onboarding Walkthrough | Published | Public |
| CCW Boardroom EP001 | Processing | Unlisted |
Compare against data/videos/video-registry.json upload status.
Requires user confirmation before proceeding.
"Ready to upload [filename]. This will open the upload dialog. Confirm?"
After confirmation:
For Episode 1 title and description, read from:
video/remotion/src/data/episode-1.json
mcp__Claude_in_Chrome__form_input: { selector: "#title-textarea", text: "[title from JSON]" }
mcp__Claude_in_Chrome__form_input: { selector: "#description-textarea", text: "[description from JSON]" }
mcp__Claude_in_Chrome__computer: { action: "screenshot" }
Report: video URL, scheduled time, visibility setting.
In the description field, append YouTube chapter markers from videoBrief.youtube.chapters:
0:00 Intro
0:05 Intelligence Brief
0:35 Build Status
...
data/videos/video-registry.json with:data/heygen/video-registry.json with:
origin/ai-updates
youtube_url: the new video URLupload_status: "uploaded"youtube_video_id: extracted from the URLYouTube API quota: 10,000 units/day. Resets midnight Pacific. Upload = 1,600 units. Max ~6 uploads per day via API.
Browser upload has no API quota. Use this skill for bulk upload days.
Version: 1.0
Created: April 2026
Tools: mcp__Claude_in_Chrome__*
Related files: scripts/youtube_upload.py, data/videos/video-registry.json
content-media
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
data-ai
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
tools
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
development
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)