agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/youtube-publisher/SKILL.md

youtube-publisher

Skill2 starsChanged 2 months agoMITView on GitHub

Upload or update a video on the user's confirmed YouTube channel with verified metadata, processing state and requested visibility.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the actual final file, title, description, thumbnail and the user's requested visibility/schedule.

    line 8
  2. Distinctive:

    When the user authorized upload, execute that scope.

    line 14
  3. Distinctive:

    Verify processing status, final metadata, thumbnail, captions and access state with readback.

    line 16

“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

Publish the reviewed package

Read the actual final file, title, description, thumbnail and the user's requested visibility/schedule. This skill bundles no uploader, OAuth client or channel connection.

Inspect the connected tool's documented operations and verify the exact channel identity. Keep tokens and OAuth files in the tool's auth store or ignored private files. Missing credentials are not a reason to copy another project's connection.

Build a concrete upload package: final file, metadata, thumbnail, captions, playlist if requested, visibility and schedule/time zone. Check current platform requirements and available quota through official docs/tools. A request to prepare packaging does not authorize publication.

When the user authorized upload, execute that scope. Record the returned video ID before downstream steps. Query existing state after ambiguous results instead of uploading a duplicate. Apply only the requested visibility and schedule.

Verify processing status, final metadata, thumbnail, captions and access state with readback. Report the video URL and distinguish uploaded, processing, scheduled and public. A successful API response is not proof that all processing or public availability has completed.

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.