agentleFS
eschotaeschota/AIGent/.claude/skills/youtube-upload/SKILL.md

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

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
  1. Very specific:

    After sign-in YouTube may show a channel picker (youtube.com/signin_prompt): click the channel by its name, then wait for …

    line 43
  2. Very specific:

    Verify independently: an anonymous fetch of youtube.com/oembed?url=<watch url>&format=json returns the title and channel once the video is …

    line 55

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. chrome_open with https://studio.youtube.com/. If the result carries sign_in_required (a Google sign-in page), tell the owner to sign in in the AIGent Chrome window that just opened and keep calling chrome_wait with url_contains: studio.youtube (50 s per call) until it passes; never type credentials yourself.
  2. Open the upload dialog: click the Create button (aria-label "Create"/"Создать", top right), then the menu item Upload videos ("Загрузить видео"). Alternative: chrome_open https://studio.youtube.com/upload directly.
  3. chrome_upload with the absolute path of the file; the dialog owns an input[type=file], so no OS dialog appears. Then chrome_wait for text "Details"/"Сведения" (up to 120 s).
  4. Details step: chrome_type the 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 with chrome_snapshot.
  5. 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/… or https://youtu.be/...) from the snapshot before clicking Publish/Save ("Опубликовать").
  6. chrome_wait for text "Video published"/"Видео опубликовано" (or the dialog with the link), chrome_screenshot for the record, then report the watch?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 for studio.youtube.com/channel/<id>.
  • https://studio.youtube.com/upload answered "Oops, something went wrong": open the channel dashboard, click Create (ref from the snapshot), then Upload videos.
  • chrome_upload with selector: 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_wait for "Video published".
  • Verify independently: an anonymous fetch of youtube.com/oembed?url=<watch url>&format=json returns 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.