docs(skills): add cloud render + variables to CLI skill, media-use generative use cases#2356
Merged
Merged
Conversation
miguel-heygen
force-pushed
the
docs/cli-cloud-render-and-media-use-cases
branch
from
a5c9afc to
28e354b
Compare
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…nerative use cases The hyperframes-cli skill only documented self-managed AWS Lambda rendering; the zero-infra HeyGen-hosted `cloud render` path (a real, shipped command with its own docs page) was absent from every skill, so agents never surfaced it. - hyperframes-cli: add `cloud` to the frontmatter verb list + entry point; new Cloud and Variables sections; new references/cloud.md distilled from docs/deploy/cloud.mdx; routing + workflow rows. - media-use: add image-to-video recipe (heygen video create type:image) plus a table of other HeyGen generative use cases (photo avatar, digital twin, video translation, lipsync, voice design) in references/operations.md; surface them in the SKILL coverage/provider rows. - Sync README + docs/guides/skills.mdx catalog entries to mention cloud render.
Verified against the installed heygen CLI (v0.3.0): no capability gap that would need the raw API. Replace hardcoded body-field lists with a pointer to `heygen video create --request-schema` (self-documenting, can't rot), correct the image-to-video motion_prompt/expressiveness support, and add the cinematic_avatar, ai-clipping, and photo-avatar creation paths.
The prior regen was polluted by the gitignored skills/media-use/eval-report.html (a suppressed mv error left it present), so the committed media-use hash didn't match a clean checkout. Regenerate with no untracked artifacts present.
miguel-heygen
force-pushed
the
docs/cli-cloud-render-and-media-use-cases
branch
from
ec70df5 to
e7142ca
Compare
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Close a skill-discovery gap and add generative media use cases:
hyperframes-cli: document the zero-infra HeyGen-hostedcloud renderpath (previously absent from every skill) and the CLI variables/template surface.media-use: add image-to-video and other HeyGen generative use cases.Why
hyperframes cloud renderis a real, shipped command group (packages/cli/src/commands/cloud/→ render/list/get/delete) with a full docs page (docs/deploy/cloud.mdx), but no skill mentioned it. The only cloud-render path skills knew was self-managedlambda(AWS). An agent asked to "render in the cloud" would reach for the heavy AWS setup and never surface the zero-infra option the docs actually lead with. The two are distinct products:cloud render= HeyGen-hosted, pay-per-credit;lambda= bring-your-own-AWS distributed rendering.Separately, media-use documented avatar/LTX video generation but not image-to-video (animate any still into a lip-synced talking clip) or the other HeyGen generative endpoints, which are reachable through the
heygenCLI it already uses.How
cloudto the frontmatter verb list + a HeyGen-hosted entry point; new Cloud and Variables sections; routing + workflow rows split into zero-infra (cloud) vs bring-your-own-AWS (lambda).docs/deploy/cloud.mdx— auth model, render pipeline, flags, upload-once/re-render-many template loop, webhooks, idempotency. Full variables schema stays inhyperframes-core(no duplication).heygen video create -d '{"type":"image",…}', a raw/v3/videosbody variant — not a new wrapped verb, per the "guides not wraps" convention) + a table of other generative use cases (photo avatar, digital twin, video translation, lipsync, voice design) with doc slugs.README.md+docs/guides/skills.mdxcatalog entries to mention cloud render (per the repo's skill-catalog-maintenance rule).Test plan
media-usecoverage tests pass (13/13,scripts/lib/coverage.test.mjs)packages/cli/src/commands/cloud/), the docs (docs/deploy/cloud.mdx,docs/concepts/variables.mdx), and the HeyGen developer docs (image-to-video)Not covered: no changes to CLI code,
lambda.md, or thehyperframes-corevariables reference; the pre-existing untrackedskills/media-use/launch.htmlis intentionally excluded.