Meeting breakdown
Generate a visual meeting breakdown (HTML) with speaker timeline, topic labels, chapter summaries, and action items from a meeting recording. Use when the user wants meeting notes, a recap, action items, or a who-said-what timeline from a recorded meeting or call. Takes one source: a local video file, URL, or cloudglue:// file URI (e.g. cloudglue://files/<id>). Runs the built-in tinycloud "meeting-breakdown" 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 meeting-breakdownAssembled 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.8 KB, as published. Nobody here has run it
Meeting breakdown
This skill is a thin wrapper around the meeting-breakdown workflow recipe
bundled inside the tinycloud binary (watch → extract ×2 → render).
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 meeting-breakdown --json -
Run it with the user's source. The analysis steps (one describe + two extracts) 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 meeting-breakdown $source --json(free).tinycloud workflow meeting-breakdown $source --jsonUseful params:
--param segment=chapters(default; semantic meeting narrative) or--param segment=uniform:20for dense raw intervals;--param out=<path>to control 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 breakdown path is
data.outputs.html(also indata.artifacts[]). Default:./tinycloud-output/runs/<data.run_id>/meeting-breakdown.html. - Report the HTML path; offer
tinycloud publish <html> --name meeting-breakdown --visibility private --jsonto host it as a shareable page. Share the returneddata.url(fresh content can take ~1 min to appear there;data.version_urlis live immediately, so a brief 403 atdata.urlis not a failure).
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.