Default: Claude native translation (no API key needed)
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionomnicaptions-translateExecute the skills CLI command in your project's root directory to begin installation:
Fetches omnicaptions-translate from lattifai/omni-captions-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate omnicaptions-translate. Access via /omnicaptions-translate in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
21
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
21
stars
Default: Claude native translation (no API key needed)
Use Gemini API only when user explicitly requests it.
_Claude_{lang} suffixUse CLI when user requests Gemini:
omnicaptions translate input.srt -l zh --bilingual
Output: input_Gemini_zh.srt
/omnicaptions:transcribe)/omnicaptions:convert)pip install omni-captions-skills --extra-index-url https://lattifai.github.io/pypi/simple/
Priority: GEMINI_API_KEY env → .env file → ~/.config/omnicaptions/config.json
If not set, ask user: Please enter your Gemini API key (get from https://aistudio.google.com/apikey):
Then run with -k <key>. Key will be saved to config file automatically.
LLM-based translation is superior to traditional machine translation because it understands context across multiple lines:
| Approach | Problem | Result |
|---|---|---|
| Line-by-line | No context | Robotic, disconnected translations |
| Batch + Context | Sees surrounding lines | Natural, coherent dialogue |
┌─────────────────────────────────────────┐
│ Batch size: 30 lines │
│ Context: 5 lines before/after │
├─────────────────────────────────────────┤
│ [5 previous lines] → context │
│ [30 current lines] → translate │
│ [5 next lines] → preview │
└─────────────────────────────────────────┘
Benefits:
# Original + Translation (for language learning)
omnicaptions translate input.srt -l zh --bilingual
Output example:
1
00:00:01,000 --> 00:00:03,500
Welcome to the show.
欢迎来到节目。
2
00:00:03,500 --> 00:00:06,000
Thank you for having me.
感谢邀请我。
For domain-specific or branded content:
# Use glossary for consistent terminology
omnicaptions translate input.srt -l zh --glossary terms.json
Glossary format:
{
"API": "接口",
"Token": "令牌",
"Machine Learning": "机器学习"
}
Benefits:
For specialized content, use custom prompts:
from omnicaptions import GeminiCaption
gc = GeminiCaption()
gc._translation_prompt = """
You are translating captions for a medical documentary.
Use formal Chinese medical terminology.
Glossary: {glossary}
"""
gc.translate("input.srt", "output.srt", "zh")
| Model | Best For |
|---|---|
gemini-3-flash-preview |
Fast, everyday content |
gemini-3-pro-preview |
Complex, nuanced content |
Bilingual captions let viewers verify translation quality - ideal for:
# Translate (auto-output to same directory)
omnicaptions translate input.srt -l zh # → ./input_Gemini_zh.srt
# Specify output file or directory
omnicaptions translate input.srt -o output/ -l zh # → output/input_Gemini_zh.srt
omnicaptions translate input.srt -o zh.srt -l zh # → zh.srt
# Bilingual output (original + translation)
omnicaptions translate input.srt -l zh --bilingual
# Specify model
omnicaptions translate input.vtt -l ja -m gemini-3-pro-preview
| Option | Description |
|---|---|
-k, --api-key |
Gemini API key (auto-prompted if missing) |
-o, --output |
Output file or directory (default: same dir as input) |
-l, --language |
Target language code (required) |
--bilingual |
Output both original and translation |
-m, --model |
Model name (default: gemini-3-flash-preview) |
-v, --verbose |
Verbose output |
| Language | Code |
|---|---|
| Chinese (Simplified) | zh |
| Chinese (Traditional) | zh-TW |
| Japanese | ja |
| Korean | ko |
| English | en |
| Spanish | es |
| French | fr |
| German | de |
All formats from lattifai-captions: SRT, VTT, ASS, TTML, JSON, Gemini MD, etc.
| Mistake | Fix |
|---|---|
| No API key | Use -k YOUR_KEY or follow the prompt |
| Wrong language code | Use ISO codes: zh, ja, en, etc. |
| Lost formatting | ASS styles preserved; SRT basic only |
| Inconsistent terms | Use glossary for technical content |
| Skill | Use When |
|---|---|
/omnicaptions:transcribe |
Need transcript first |
/omnicaptions:LaiCut |
Align timing before translation |
/omnicaptions:convert |
Convert format after translation |
/omnicaptions:download |
Download captions to translate |
Important: Generate bilingual captions AFTER LaiCut alignment.
File naming convention - preserve language tag and processing chain:
video.en.vtt → video.en_LaiCut.json → video.en_LaiCut.srt → video.en_LaiCut_Claude_zh.srt → video.en_LaiCut_Claude_zh_Color.ass
| 翻译方式 | 后缀 | 示例 |
|---|---|---|
| Claude (默认) | _Claude_zh |
video.en_LaiCut_Claude_zh.srt |
| Gemini API | _Gemini_zh |
video.en_LaiCut_Gemini_zh.srt |
# 1. LaiCut 对齐 (保留词级时间)
omnicaptions LaiCut video.mp4 video.en.vtt
# → video.en_LaiCut.json
# 2. 转换为 SRT (翻译用，文件小)
omnicaptions convert video.en_LaiCut.json -o video.en_LaiCut.srt
# 3a. Claude 翻译 (默认)
# → video.en_LaiCut_Claude_zh.srt
# 3b. 或 Gemini 翻译
omnicaptions translate video.en_LaiCut.srt -l zh --bilingual
# → video.en_LaiCut_Gemini_zh.srt
# 4. 转换为带颜色的 ASS
omnicaptions convert video.en_LaiCut_Claude_zh.srt -o video.en_LaiCut_Claude_zh_Color.ass \
--line1-color "#00FF00" --line2-color "#FFFF00"
LaiCut outputs JSON with word-level timing. For translation, convert to SRT first (much smaller):
# JSON (word-level, ~150KB) → SRT (segment-level, ~15KB)
omnicaptions convert video.en_LaiCut.json -o video.en_LaiCut.srt
Why? JSON preserves word timing for karaoke, but translation only needs segment text. SRT is 10-20x smaller.
| Feature | Claude (Default) | Gemini API |
|---|---|---|
| API Key | None needed | Required |
| Invocation | Skill (Read/Write) | CLI command |
| Output suffix | _Claude_{lang} |
_Gemini_{lang} |
| Best for | Most tasks | Large files, automation |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
We added omnicaptions-translate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in omnicaptions-translate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
omnicaptions-translate reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for omnicaptions-translate matched our evaluation — installs cleanly and behaves as described in the markdown.
omnicaptions-translate reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in omnicaptions-translate — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
omnicaptions-translate is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
omnicaptions-translate is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: omnicaptions-translate is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for omnicaptions-translate matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 38