agentleFS
Sign inStart free
venetanjivenetanji/creative-skills/youtube-upload/SKILL.md

youtube-upload

Skill5 starsChanged 33 days agoMITView on GitHub

Use when publishing or resuming a finished MP4 on YouTube, choosing private/unlisted/public visibility, or checking upload versus transcoding status.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use linkedin-post.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LangChainSkill

    linkedin-post

    Write a LinkedIn post based on research findings or a given topic. Use this skill when asked to create LinkedIn content, professional posts, or thought leadership pieces.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    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. Distinctive:

    Use for final YouTube delivery after a video is approved.

    line 8
  2. Distinctive:

    Only an explicitly authorized account holder/credential operator may perform OAuth or upload actions.

    line 15
  3. Distinctive:

    Never initiate consent, change OAuth scopes, enable cloud APIs, or broaden privacy without applicable authorization from the relevant …

    line 20
  4. Distinctive:

    Do not create a second upload to test this skill.

    line 22
  5. Very specific:

    Keep resumable state outside the repository and workspace in a user-owned 0700 directory, with the state file 0600.

    line 37
  6. Very specific:

    Treat a returned video ID and videos.list read-back as upload verification, not proof transcoding is finished.

    line 46
  7. Distinctive:

    Run focused tests without network or credentials:

    line 51

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

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

YouTube Upload

Use for final YouTube delivery after a video is approved. This skill uses the YouTube Data API v3 resumable upload protocol; it does not generate or modify media. Read the operating workflow before execution.

Access boundary

  • Only an explicitly authorized account holder/credential operator may perform OAuth or upload actions. A shared skill install does not grant access to Gio's personal Google account. If you do not already have approved credentials and the YouTube upload scope, route execution to Zeus/the personal credential holder; do not request, copy, or expose secrets.
  • Never initiate consent, change OAuth scopes, enable cloud APIs, or broaden privacy without applicable authorization from the relevant account holder.
  • Do not create a second upload to test this skill. Use mocked tests and the saved private state to resume an approved upload.

Run and verify

  1. Confirm the approved source file, destination channel ID, title, category, privacy, and notification choice. Default visibility is private; request unlisted or public only when explicitly specified. The uploader confirms that the authorized account owns the expected channel before creating or resuming any upload; it needs an existing read scope that allows channels.list.
  2. On the authorized host, read the live gog --version and gog youtube --help. If no native video-upload command is available, use scripts/youtube_upload.py with the operator-owned private token helper; do not pass access/refresh tokens on command lines or put them in environment dumps, logs, the repository, or shared state.
  3. Keep resumable state outside the repository and workspace in a user-owned 0700 directory, with the state file 0600. The state and its .lock sibling contain coordination metadata; the state contains a resumable session URL until completion. The uploader fingerprints the source and binds resume state to account, channel, title, category, privacy, and notifications.
  4. The script defaults to private and notifySubscribers=false. A run uses one session, reconciles server position before chunks and after ambiguous failures, and never silently creates a replacement session. An ambiguous session-start response requires account reconciliation before retrying.
  5. Treat a returned video ID and videos.list read-back as upload verification, not proof transcoding is finished. Check the actual channel and privacy; report processingStatus separately. The script never calls videos.update or silently changes privacy.

Run focused tests without network or credentials:

python3 -m unittest discover -s youtube-upload/tests -v

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.

Check your setup, free