yt-upload SKILL.md skillA
yt-upload from uplika/uplika-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uplika/uplika-plugin/yt-upload@git:20261017.0a2c1dePins git:20261017.0a2c1de in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uplika/uplika-plugin
- Path
skills/yt-upload/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261017.0a2c1de, committed Oct 17, 2026
- First version recorded
- Oct 9, 2026
- Size
- 7,536 bytes
- Repository stars
- 6
- License
- MIT
Upload a video to YouTube with the right options: title, description, tags, language, privacy, thumbnail; asks about made-for-kids.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# yt-upload One video to the person's connected YouTube channel, with every option set on purpose. Use it whenever a video goes to YouTube through Uplika: a finished long video, a Short (`yt-shorts` sends the file here), or a slot from `yt-plan`. For the title and thumbnail use `yt-package` first; for the description and tags, `yt-seo`. ## Before you start 1. Read YouTube's rules from `list_platforms` (the YouTube entry), never from memory: the title limit and how it is counted, the description limit and how it is counted, the accepted video files, the `shorts` rule, and `options`, the schema of every `options.youtube` field. (Uplika's publish-options tool is for TikTok only; it does not apply to YouTube.) 2. Call `select_channels` with scope `youtube`. It returns the `accountIds` to pass to `publish`, and `skipped` with a sentence and a reconnect link when the connection has expired. Nothing connected: send the person to https://uplika.com/dashboard/connections. 3. If a call answers `workspace_required`, show the workspaces it lists, ask which one, and pass `workspaceId` on every later call, `publish` included. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_b6efl27rfocstvhl/f3a7ba7f7c3ff63e51903ffaafddd24f1ec7b17d3c581cb7960c292354b5bf4b.json
Then /plugin install yt-upload@markdownregistry-b6efl27rfocstvhl in Claude Code. It installs git:20261017.0a2c1de, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add uplika/uplika-plugin/yt-upload@sha256:f3a7ba7f7c3ff63eThe line at the top of this page pins the label git:20261017.0a2c1de, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_b6efl27rfocstvhl)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in uplika/uplika-plugin/yt-upload since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of yt-upload from somewhere else? Ask it: where did my yt-upload come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 17, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.0a2c1de latest | 2026-10-17 | 0a2c1de | 7,536 B | A | view · diff |
| git:20261009.4206a03 | 2026-10-09 | 4206a03 | 7,046 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/yt-upload/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7536 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
uplika/uplika-plugin · 6 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b6efl27rfocstvhl GET https://markdownregistry.com/api/v1/resolve?ref=uplika/uplika-plugin/yt-upload GET https://markdownregistry.com/api/v1/blob/f3a7ba7f7c3ff63e51903ffaafddd24f1ec7b17d3c581cb7960c292354b5bf4b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.