Youtube publish
Generate YouTube publishing metadata from a video: title, description, chapter markers, tags, SRT subtitles, and an HTML copy page to paste from. Use when the user is preparing a video for YouTube upload and wants the metadata and subtitles generated. Takes one source: a local video file, URL, or cloudglue:// file URI (e.g. cloudglue://files/<id>). Runs the built-in tinycloud "youtube-publish" workflow; requires the tinycloud CLI configured with a Cloudglue API key (analysis runs through the user's Cloudglue account).From its SKILL.md
npx -y skills add cloudglue/tinycloud --skill youtube-publishAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, as published. Nobody here has run it
YouTube publish kit
This skill is a thin wrapper around the youtube-publish workflow recipe
bundled inside the tinycloud binary (watch → extract → thumbnails → captions → render). It generates SRT subtitles itself as part of the run.
Run
-
Check the CLI. If the general
tinycloudskill is installed alongside this one, run itsscripts/preflight.sh. Otherwise verify directly:tinycloud setup --check --json # ready when data.ok == trueMissing CLI:
npm install -g @cloudglue/tinycloud(see https://tinycloud.sh). Missing key:tinycloud setup cloudglue --api-key <key>. -
Confirm the recipe is available (free, no cloud calls):
tinycloud workflow validate youtube-publish --json -
Run it with the user's source. The analysis steps run through the configured Cloudglue API key — if the user has not clearly asked to run it, show the step plan first with
tinycloud workflow plan youtube-publish $source --json(free).tinycloud workflow youtube-publish $source --jsonUseful params:
--param segment=chapters(default; produces the chapter markers YouTube descriptions need) or--param segment=uniform:20for a lighter pass on short videos;--param out=<path>for the HTML location.
Read the result
Parse the single JSON envelope from stdout (machine output; logs are stderr):
- Success:
status == "ready"anddata.status == "completed". - The copy page is
data.outputs.html; the run dir also contains the generated SRT undercaptions/(listed indata.artifacts[]). Default:./tinycloud-output/runs/<data.run_id>/youtube-publish.html. - Report the HTML path and the SRT path. The page renders even when subtitles were unavailable.
Any other status (needs_credentials, needs_upload, pending, paused,
error) or data.status of partial/failed: stop, report the envelope's
error.message, and follow its setup / resume / next hints. The general
tinycloud skill (if installed) documents full status handling.