agentleFS
nexmoenexmoe/VidBee/skills/video-localization/SKILL.md

video-localization

Skill11k starsChanged 48 days agoMITView on GitHub

Coordinate the translate skill, bilingual subtitle exports, subtitled videos and synchronized local dubbing. Use for video localization, bilingual subtitles, or dubbed videos.

2 other projects use a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 3 mentionsJan 2026: 4 mentionsFeb 2026: 0 mentionsMar 2026: 2 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 2 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the nexmoe/VidBee repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about nexmoe/VidBee

The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 17

Talked about on Bluesky, YouTube, GitHub and the web (17 times).

On Bluesky · 12

7 more on Bluesky

On YouTube · 3

On GitHub · 1

On the web · 1

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the attached video's existing download, transcript, and timestamps.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Video localization

Use the attached video's existing download, transcript, and timestamps. Never ask the user to install Python or deploy another application. Preserve original media and subtitles.

  1. Establish the requested deliverables and target language when provided. Load the installed translate skill using the native read tool and its path from the available skill catalog. Follow it in this session, passing the requested target language, any explicit subtitle layout limits, whether dubbing is requested and the requirement for a complete saved subtitle track. It owns language defaults, existing-track reuse, terminology, translation, polishing, subtitle length/width constraints, split/alignment rechecks, timing and batch saves. Its required references/subtitle-constraints.txt supplies the adapted VideoLingo policy. If that skill or policy is unavailable, report the missing dependency rather than improvising a second translation workflow.
  2. Continue only after translate has verified the complete track and returned its actual sourceKey and any subtitleLayout exceptions. A saved track alone does not prove layout compliance. Report unresolved default-budget exceptions alongside usable outputs; an unresolved strict user limit remains an incomplete requirement. If requested, load export_subtitles with that key: srt/vtt exports files, mkv muxes selectable subtitles, and mp4 burns subtitles. bilingual=true includes the currently viewed original text without changing the user's source selection; target line breaks do not reflow that original track. Preserve its timing rather than copying upstream gap filling or short-cue extension.
  3. For dubbing, follow translate section 6 to prepare contextual numeric readings and any necessary spoken repairs. Load manage_tts_model and search the official sherpa-onnx catalog with action=status, query, language or family; follow nextOffset for more results. The available models extend beyond the original presets. Use refresh=true for newly published models. Inspect the saved default, language hints, download size, voice defaults/ranges and installed state. Honor the requested model; otherwise use the saved default when compatible. If another model is required for the target language, choose a compatible model for this call and explain the choice. Pass its exact modelId to create_dubbed_video for this task; use action=select only when the user requests a persistent default change. Models and required vocoders/phonemizers download automatically on first use. Use action=prepare to inspect actual native voice ranges and bundled reference WAVs before choosing a specific voice. Omit voice for the model's language default; IDs are model-specific. Pocket and ZipVoice require reference audio: reference.file is a bundled WAV name returned by preparation, relative to the model directory. ZipVoice also requires reference.text to exactly transcribe that WAV; use its returned transcript or verified publisher documentation, never invent one. Pocket can use a bundled default reference without text. Load create_dubbed_video with the verified sourceKey and its sparse speechOverrides; these bind one-based saved cue indices and exact originalText to spoken text without rewriting display subtitles. Choose background=separate to preserve accompaniment while removing original vocals, or remove when the user wants dubbed voice only. Do not describe source separation as voice cloning. Keep the default maximum speed unless the user requests another limit. If a cue cannot fit, pass the actual fitting error back to translate, shorten only that cue's spoken wording without losing meaning, and retry the same sourceKey while retaining all valid overrides. Limit the whole request to 3 dubbing attempts, then report remaining failures. Verify the tool's actual modelId, voice and applied override count. Never silently cut off words or claim success after an error.
  4. Deliver the requested outputs and their saved paths. Distinguish saved subtitles from a completed rendered video. A tool failure or partial translation is not a finished deliverable. Avoid a lengthy narration of intermediate steps.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.