How do I install the Heygen Video Localization skill?

Run npx skillmds@latest add luzw6688-prog/heygen-video-localization in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Heygen Video Localization safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Heygen Video Localization?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Heygen Video Localization free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Heygen Video Localization?

luzw6688-prog (@luzw6688-prog) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Heygen Video Localization by luzw6688-prog

Name: Heygen Video Localization
Author: luzw6688-prog

Heygen Video Localization

Translate an existing spoken video with HeyGen, replace the original narration in a target language, create lip-synced output, and deliver a video with visible burned-in target-language subtitles. Use when a user asks to dub, translate, localize, add subtitles to, or replace speech in an existing video.

luzw6688-prog Updated Sep 22, 2026

File contents

HeyGen Video Localization

Workflow

Confirm the source video, target language, and whether captions must be visibly burned into the final MP4. Obtain explicit authorization before uploading private video to HeyGen.
Submit the source through heygen_create_video_translation, with the target language, enableCaption: true, and mode: precision. Enable speech enhancement unless the user asks otherwise.
Poll heygen_get_video_translation until completed. Preserve the returned translated MP4 and SRT/VTT files.
Do not assume enableCaption has burned captions into the MP4. Inspect a frame during an active subtitle cue.
If captions are not visible, render the SRT locally into a new MP4. Use white, centered text near the lower third with a thin black outline by default. Add a translucent background only when requested.
Verify a representative output frame and confirm that translated audio remains present before delivery.

Safety and Output Rules

Treat a HeyGen upload as an external disclosure. Explain the destination and request approval when the user has not already provided it.
Do not remove copyright, platform, or provenance watermarks.
If a third-party FFmpeg binary must be downloaded or run, explain the risk and obtain explicit authorization first. Prefer a locally trusted encoder or macOS AVFoundation when available.
Keep the translated source untouched. Save the rendered result with a distinct name such as <stem>-<language>-subtitled.mp4.

Delivery

Provide the final MP4, its duration and target language. State that subtitles are burned into the image. Offer SRT/VTT separately only if the user needs an editable subtitle track.

---name: heygen-video-localizationdescription: Translate an existing spoken video with HeyGen, replace the original narration in a target language, create lip-synced output, and deliver a video with visible burned-in target-language subtitles. Use when a user asks to dub, translate, localize, add subtitles to, or replace speech in an existing video.---# HeyGen Video Localization## Workflow1. Confirm the source video, target language, and whether captions must be visibly burned into the final MP4. Obtain explicit authorization before uploading private video to HeyGen.2. Submit the source through `heygen_create_video_translation`, with the target language, `enableCaption: true`, and `mode: precision`. Enable speech enhancement unless the user asks otherwise.3. Poll `heygen_get_video_translation` until completed. Preserve the returned translated MP4 and SRT/VTT files.4. Do not assume `enableCaption` has burned captions into the MP4. Inspect a frame during an active subtitle cue.5. If captions are not visible, render the SRT locally into a new MP4. Use white, centered text near the lower third with a thin black outline by default. Add a translucent background only when requested.6. Verify a representative output frame and confirm that translated audio remains present before delivery.## Safety and Output Rules- Treat a HeyGen upload as an external disclosure. Explain the destination and request approval when the user has not already provided it.- Do not remove copyright, platform, or provenance watermarks.- If a third-party FFmpeg binary must be downloaded or run, explain the risk and obtain explicit authorization first. Prefer a locally trusted encoder or macOS AVFoundation when available.- Keep the translated source untouched. Save the rendered result with a distinct name such as `<stem>-<language>-subtitled.mp4`.## DeliveryProvide the final MP4, its duration and target language. State that subtitles are burned into the image. Offer SRT/VTT separately only if the user needs an editable subtitle track.

Frequently asked questions