youtube-upload
Skill2 starsChanged 2 months agoMITView on GitHub
Upload a video to the owner's YouTube channel through their own Chrome with the chrome_* tools (YouTube Studio, shadow DOM, file input without a dialog), and where the DynIvy reel metadata lives.
8 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- runehub-ai/rune-hubedited, first seen Nov 15, 2026
- venetanji/creative-skillstheir own version, first seen Nov 1, 2026
- dreammis/social-auto-uploadtheir own version, first seen Oct 25, 2026
- Perufitlife/postwire-skillstheir own version, first seen Oct 15, 2026
- allthriveai/amplifytheir own version, first seen Aug 30, 2026
- thapar25/claude-skillstheir own version, first seen Aug 12, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- runehub-ai/rune-hub★ 621% same
Wrote their own version · 7
- dreammis/social-auto-upload★ 16ksame name
- kevinbadi/ai-os-skills★ 69same name
- venetanji/creative-skills★ 5same name
- allthriveai/amplify★ 0same name
- BlackLotus1974/claude-skills★ 0same name
- Perufitlife/postwire-skills★ 0same name
- thapar25/claude-skills★ 0same 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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aigent-farmSkill
- aigent-selfdevSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 43
After sign-in YouTube may show a channel picker (youtube.com/signin_prompt): click the channel by its name, then wait for …
- Very specific: line 55
Verify independently: an anonymous fetch of youtube.com/oembed?url=<watch url>&format=json returns the title and channel once the video is …
“Common” is measured: kept by at least 6 in 10 of the 5 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
Publishing a video on the owner's YouTube channel
AIGent's Chrome window is the tool: mcp__aigent__chrome_open starts a visible Chrome on AIGent's
own profile (the owner's everyday Chrome cannot be driven: Chrome 136+ ignores the DevTools port on
the default profile), and the other chrome_* tools read and drive the tab. The owner signs in to
Google there once, by hand; the login persists in that profile. YouTube Studio is Polymer: everything sits in shadow DOM, which chrome_snapshot walks; act
through refs from the latest snapshot, and take a new snapshot after every click that changes the
page.
The flow that works
chrome_openwithhttps://studio.youtube.com/. If the result carriessign_in_required(a Google sign-in page), tell the owner to sign in in the AIGent Chrome window that just opened and keep callingchrome_waitwithurl_contains: studio.youtube(50 s per call) until it passes; never type credentials yourself.- Open the upload dialog: click the Create button (aria-label "Create"/"Создать", top right),
then the menu item Upload videos ("Загрузить видео"). Alternative:
chrome_openhttps://studio.youtube.com/uploaddirectly. chrome_uploadwith the absolute path of the file; the dialog owns aninput[type=file], so no OS dialog appears. Thenchrome_waitfor text "Details"/"Сведения" (up to 120 s).- Details step:
chrome_typethe title into the title box (role textbox, label "Add a title" or the current title),clear: true; the description into the description box. Below, choose the audience: No, it's not made for kids (radio). Click Next ("Далее") three times (Video elements, Checks, Visibility), waiting for each page withchrome_snapshot. - Visibility step: pick Public/Unlisted/Private as the owner said (the Asset Store
media link needs Public). Copy the video link shown on that page (text
youtu.be/…orhttps://youtu.be/...) from the snapshot before clicking Publish/Save ("Опубликовать"). chrome_waitfor text "Video published"/"Видео опубликовано" (or the dialog with the link),chrome_screenshotfor the record, then report thewatch?v=URL. Processing may continue on YouTube's side; that does not block the link.
Refs go stale after any page change; a failed chrome_click means "snapshot again". Never type
the owner's password anywhere: a sign-in page is theirs to handle.
What worked on 2026-09-12 (Dynamic Ivy reel, 4 minutes end to end)
- After sign-in YouTube may show a channel picker (
youtube.com/signin_prompt): click the channel by its name, then wait forstudio.youtube.com/channel/<id>. https://studio.youtube.com/uploadanswered "Oops, something went wrong": open the channel dashboard, click Create (ref from the snapshot), then Upload videos.chrome_uploadwithselector: input[type=file]accepted the absolute path; the Details step appeared within seconds while the file kept uploading.- Stable selectors inside the dialog: title
ytcp-video-title #textbox(contenteditable), description#description-textarea #textbox, Next#next-button(three times), Publish#done-button; the video link (youtu.be/…) is visible on the Visibility step before publishing. Refs shift while the upload progress re-renders — prefer these selectors there. - YouTube warns when copyright checks are still running; wait for "Checks complete" before
Publish (the agent did, about a minute), then
chrome_waitfor "Video published". - Verify independently: an anonymous fetch of
youtube.com/oembed?url=<watch url>&format=jsonreturns the title and channel once the video is public.
DynIvy reel
Everything for the Dynamic Ivy reel is prepared in R:\AssetStore\ASStore26\DynIvy\store-listing\YOUTUBE.md:
the file (R:\DynIvy-hq\reel\DynIvy_Reel_1080p.mp4, 59 s, 1080p60), the exact title, the
description (each paragraph one line, paste as is — it carries the AI/ML disclosure that must not be
dropped), visibility public, and what to do with the URL afterwards (youtube-receipt.json,
product.json under media.video.youtube, SUBMISSION.md). Read that file first; do not invent a
title or description.
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.

