Use when generating subtitles with KrillinAI CLI from a YouTube link, Bilibili/local video, or existing media, including platform caption download, Whisper fallback, translation, bilingual SRT, and short vertical subtitle output.
77
96%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Use this skill for the subtitle stage.
./build/krillinai-cli subtitle "<input>" \
--origin-lang en \
--target-lang zh_cn \
--workdir tasks/demo \
--caption-source anyBuild the CLI first if needed:
go build -o build/krillinai-cli ./cmd/cli--caption-source any; platform captions are used first, then Whisper fallback.local:/abs/path/video.mp4 or a path accepted by the CLI.| Flag | Use |
|---|---|
--origin-lang | Source language, such as en, zh, ja |
--target-lang | Target language, such as zh_cn |
--workdir | Dedicated task directory |
--caption-source any | Prefer platform captions, fallback to transcription |
--caption-source whisper | Force transcription |
--bilingual-top=true | Put target language on top in bilingual SRT |
--dry-run | Validate without downloads or AI calls |
Read paths from krillinai_manifest.json. Main files:
origin_language_srt.srttarget_language_srt.srtbilingual_srt.srtshort_origin_mixed_srt.srtorigin_video.mp4origin_audio.mp3"ok": true.krillinai_manifest.json exists under --workdir.bilingual_srt.srt ordering and short_origin_mixed_srt.srt readability.skills/krillinai-cli/references/cli-contract.md.22ee064
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.