How do I install the Krillinai Subtitle skill?

Run npx skillmds@latest add krillinai/krillinai-subtitle 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 Krillinai Subtitle safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Krillinai Subtitle?

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 Krillinai Subtitle free to use?

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

Who published Krillinai Subtitle?

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

Krillinai Subtitle by krillinai — Agent Skill

Name: Krillinai Subtitle
Author: krillinai

Krillinai Subtitle

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.

krillinai Updated Sep 17, 2026

File contents

KrillinAI Subtitle

Use this skill for the subtitle stage. Read skills/krillinai-cli/references/cli-contract.md first for binary location, execution working directory, configuration, and JSON behavior.

Command

(cd "$KRILLINAI_CWD" && "$KRILLINAI_CLI" subtitle "<input>" \
  --origin-lang en \
  --target-lang zh_cn \
  --workdir "$WORKDIR" \
  --caption-source any \
  --prepare-video)

Inputs

YouTube URL: prefer --caption-source any; platform captions are used first, then Whisper fallback.
Local file: use local:/abs/path/video.mp4 or a path accepted by the CLI.
Bilibili or other yt-dlp supported links: use when media download works; platform caption behavior may differ, so expect transcription fallback.

Important Flags

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
`--prepare-video`	Require the original video for later render stages
`--bilingual-top=true`	Put target language on top in bilingual SRT
`--subtitle-style-file`	Merge a JSON subtitle-style override
`--dry-run`	Validate without downloads or AI calls

Outputs

After a real run, read paths from krillinai_manifest.json. Main files:

origin_language_srt.srt
target_language_srt.srt
bilingual_srt.srt
short_origin_mixed_srt.srt
origin_video.mp4 when media preparation produced or required video
origin_audio.mp3 when transcription preparation produced audio

subtitle --dry-run validates command shape but does not write a manifest or output files.

Verification

Require terminal JSON with "ok": true.
Confirm krillinai_manifest.json exists under --workdir.
Spot-check bilingual_srt.srt ordering and short_origin_mixed_srt.srt readability.
When --prepare-video was requested, require a non-empty origin_video output.
For Agent integration details, read skills/krillinai-cli/references/cli-contract.md.

---name: krillinai-subtitledescription: 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.---# KrillinAI SubtitleUse this skill for the `subtitle` stage. Read `skills/krillinai-cli/references/cli-contract.md` first for binary location, execution working directory, configuration, and JSON behavior.## Command```bash(cd "$KRILLINAI_CWD" && "$KRILLINAI_CLI" subtitle "<input>" \ --origin-lang en \ --target-lang zh_cn \ --workdir "$WORKDIR" \ --caption-source any \ --prepare-video)```## Inputs- YouTube URL: prefer `--caption-source any`; platform captions are used first, then Whisper fallback.- Local file: use `local:/abs/path/video.mp4` or a path accepted by the CLI.- Bilibili or other yt-dlp supported links: use when media download works; platform caption behavior may differ, so expect transcription fallback.## Important Flags| 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 || `--prepare-video` | Require the original video for later render stages || `--bilingual-top=true` | Put target language on top in bilingual SRT || `--subtitle-style-file` | Merge a JSON subtitle-style override || `--dry-run` | Validate without downloads or AI calls |## OutputsAfter a real run, read paths from `krillinai_manifest.json`. Main files:- `origin_language_srt.srt`- `target_language_srt.srt`- `bilingual_srt.srt`- `short_origin_mixed_srt.srt`- `origin_video.mp4` when media preparation produced or required video- `origin_audio.mp3` when transcription preparation produced audio`subtitle --dry-run` validates command shape but does not write a manifest or output files.## Verification- Require terminal JSON with `"ok": true`.- Confirm `krillinai_manifest.json` exists under `--workdir`.- Spot-check `bilingual_srt.srt` ordering and `short_origin_mixed_srt.srt` readability.- When `--prepare-video` was requested, require a non-empty `origin_video` output.- For Agent integration details, read `skills/krillinai-cli/references/cli-contract.md`.

Frequently asked questions