youtube-publisher
Skill2 starsChanged 14 days agoMITView on GitHub
Upload, schedule and update YouTube videos through the official Data API with a fingerprinted approval gate: dry run shows the exact payload, the user approves, only then it publishes. Handles thumbnail, playlist, scheduling, visibility changes and metadata edits on existing videos. Not for writing metadata (use youtube-metadata-optimizer).
4 other projects use a version of this.
Adopted by
Most recently taken up by
- timscheuerai/content-vaulttheir own version, first seen Oct 15, 2026
- timscheuerai/gtm-architecture-templatetheir own version, first seen Sep 14, 2026
- wlzh/skillstheir own version, first seen Aug 28, 2026
- smixs/youtube-publishertheir own version, first seen Mar 6, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- wlzh/skills★ 694same name
- timscheuerai/content-vault★ 38same name
- smixs/youtube-publisher★ 8same name
- timscheuerai/gtm-architecture-template★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- youtube-channel-skillsSkill
- youtube-analytics-reviewerSkill
- youtube-channel-auditSkill
- youtube-comment-managerSkill
- youtube-content-plannerSkill
- youtube-idea-researchSkill
- youtube-metadata-optimizerSkill
- youtube-script-writerSkill
- youtube-shorts-repurposerSkill
- youtube-title-thumbnailSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Make sure a video.json exists and passes python3 scripts/validate_metadata.py video.json.
- Very specific: line 37
Write changes.json with only the fields to change (title, description, tags, privacyStatus, publishAt, madeForKids, thumbnail).
- Very specific: line 46
If the Google Cloud project is unaudited, uploads stay private regardless (see ../../references/api-quota.md gotcha 1).
- Very specific: line 52
Never change madeForKids or make a video public as a side effect of another request.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTube Publisher
The only skill that writes to the channel's videos. Every action is two-pass: a dry
run that prints an approval card with a fingerprint of the exact payload, and a
confirmed run with --confirm <fingerprint> that refuses to act if anything changed.
When to use
- "Upload this video", "schedule it for Tuesday 18:00", "make it public"
- "Change the title/description/thumbnail of this video"
- Bulk updates (e.g. adding a link to the last 20 descriptions), one approval per video
Prerequisites
Tier 2 (owner). Check with python3 scripts/check_config.py. If not ready, walk the
user through README.md §Setup (Google Cloud project, OAuth Desktop client,
python3 scripts/auth.py). Without Tier 2, fall back to manual mode: give a
Studio checklist with every field ready to paste.
Steps: new upload
- Make sure a
video.jsonexists and passespython3 scripts/validate_metadata.py video.json. If not, runyoutube-metadata-optimizerfirst. - Confirm the channel:
check_config.py/auth.pyprinted which channel the token controls. Say it to the user before the first write in the session. - Dry run:
python3 scripts/publish_video.py video.json. Show the approval card to the user verbatim (title, description, fields, validation, fingerprint). - Wait for explicit approval ("yes", "sí", "publica", "dale"). Edits → update
video.json→ new dry run → new fingerprint. - Confirmed run:
python3 scripts/publish_video.py video.json --confirm <fingerprint from the card>. - Report the video URL, visibility, scheduled time (in the user's time zone), thumbnail/playlist results.
- Studio-only handoff: pinned comment, end screens, cards, Test & Compare variants, subtitles check. Give the checklist from the metadata step.
Steps: update an existing video
- Write
changes.jsonwith only the fields to change (title,description,tags,privacyStatus,publishAt,madeForKids,thumbnail). - Dry run:
python3 scripts/update_video.py <url> changes.jsonshows a before/after diff and fingerprint. - Approval →
python3 scripts/update_video.py <url> changes.json --confirm <fingerprint>.
Scheduling rules
publishAtis UTC ISO 8601 in the file; always tell the user the local time too.- Scheduled uploads must be
privateuntil publish time (validator enforces it). - Upload ≥ 24 h ahead so HD processing and checks finish.
- If the Google Cloud project is unaudited, uploads stay private regardless (see
../../references/api-quota.mdgotcha 1). Tell the user before uploading, and offer to schedule from Studio instead.
Hard rules
- Never run with
--confirmwithout the user's explicit approval of that specific card in this conversation. Never compute or guess a fingerprint yourself; copy it from the card the user saw. - Approval for one video does not carry to the next one, nor to an edited payload.
- Never change
madeForKidsor make a video public as a side effect of another request. - Bulk operations: one card per video, or one card listing every video with its own fingerprint; the user approves each.
- On failure, report the error as returned. Do not retry uploads blindly (each attempt costs quota).
Files
scripts/publish_video.py,scripts/update_video.py,scripts/validate_metadata.py,scripts/check_config.py,scripts/auth.py../../references/api-quota.md../../references/metadata-limits.md
Related skills
youtube-metadata-optimizer— produces thevideo.jsonyoutube-title-thumbnail— the thumbnail file and titleyoutube-comment-manager— first-hours comment replies after publishing
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

