youtube-upload
Get a finished video onto the channel, and all the work either side of the human step. Use when a render is ready, when asked to upload or re-upload unlisted, or before reaching for videos.insert or Studio.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- youtube-upload
- description
- Get a finished video onto the channel, and all the work either side of the human step. Use when a render is ready, when asked to upload or re-upload unlisted, or before reaching for videos.insert or Studio.
03 SKILL.md 正文
Putting a video on the channel
The upload is not yours. videos.insert from an unverified project - this
one - makes a video permanently private until a compliance audit: it can
never be unlisted. Studio is no better; its file field opens the native OS
picker, which no extension can see, and the browser upload tool caps at 10 MB
per call against 100 MB-1 GB renders. A human uploads, by hand.
Before the handover
- Confirm the render: duration, dimensions, and a decoded frame, looked at: right-side-up, not mirrored. Rotation is not in the file and does not track resolution; the discarded upside-down batch passed both.
- Title: match the series exactly, capitalisation included. The card tooling
parses only
part 3(134 of 383),- 14.1 -andpt. 4, the channel's own;3/5and(3/8)are invisible to it and strand the video on an adjacency guess. - Description via
correct-youtube-description, thencheck-youtube-description; if three passes do not clear it, report rather than loop. Chapters come from the final file, after any title card - a card shifts every timestamp. - Staging sheet: a committed markdown file at the repo root
(
UPLOAD-SHEET.md): why the upload is theirs, the batch visibility, a row per video in upload order (title, absolute render path, description file), and any file that must NOT be uploaded. - Hand over the sheet and stop. Do not offer to drive Studio or write an uploader.
Replacing a video
Never two public videos under one title: upload the new one Private; record
<old>|<new> in data/archive/id-map.psv, which the retire step refuses
without; then retire the old and confirm; only then set the new one to the
batch visibility.
After the handover
You need the IDs back; nothing downstream works. Check each with
videos.list(part=status): privacyStatus: private where you asked for
unlisted means it went through the API after all - no flag flip fixes it. Then
by API: descriptions (correct-youtube-description); record the IDs where the
channel keeps them.
End screens and cards are a second human handover - no API resource exists.
correct-youtube-cards writes a worksheet for a person to apply in Studio;
stage and hand it over like the sheet.
If the constraint has changed
Only the YouTube API Services compliance audit lifts the restriction, not OAuth consent-screen verification; a report of an audit is not evidence. Ask for the audit status on that project's screen in Cloud Console and say which you rely on: approved there, uploads come out as you set them; anything else (in review, not requested, not found, consent screen only) is permanently private - hand over. The operations doc has the project's creation date; none was audited before it existed. Never settle it by uploading.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code