# Capcut Edit

Edit CapCut / JianYing video projects, read and write subtitles, timing, speed...

- Repository: https://github.com/renezander030/capcut-cli (1083 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add renezander030/capcut-cli --skill capcut-edit -g -a claude-code -y`
Codex: `npx skills add renezander030/capcut-cli --skill capcut-edit -g -a codex -y`
Cursor: `npx skills add renezander030/capcut-cli --skill capcut-edit -g -a cursor -y`
Gemini CLI: `npx skills add renezander030/capcut-cli --skill capcut-edit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add renezander030/capcut-cli`

## Description

Edit CapCut / JianYing video projects, read and write subtitles, timing, speed, volume, templates, animations (fade/ken-burns), and cut long-form to shorts. Use when the user mentions capcut, jianying, subtitles, video editing, draft_content.json, draft_info.json, or cutting videos, in English or Chinese (剪映, 字幕, 草稿, 剪辑, 切片, 视频编辑).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# capcut-edit

CLI for editing CapCut / JianYing drafts through a version-aware store. v0.11 detects and synchronizes readable timelines across `draft_content.json`, `draft_info.json`, `draft_meta_info.json`, and `template-2.tmp`.

## Project locations

- **macOS**: `~/Movies/CapCut/User Data/Projects/com.lveditor.draft/<project>/`
- **Windows**: `%LOCALAPPDATA%\CapCut\User Data\Projects\com.lveditor.draft\<project>\`
- **Windows (JianYing / 剪映)**: `%LOCALAPPDATA%\JianyingPro\User Data\Projects\com.lveditor.draft\<project>\`

## Core principle, deterministic scripts

Any recipe involving more than one `capcut` call, any arithmetic, or any branching ships as a parameterised shell script in `scripts/`. Claude invokes the script with inputs; the script runs a fixed sequence. If a recipe can be a script, it **must** be a script, not a narrative in `references/`.

`references/workflows.md` documents *which script to call and why*, never a reconstructable sequence.

## Progressive disclosure

Start broad, drill into what you need. Never dump full project JSON.

```bash
capcut info <project> -H           # overview
capcut doctor -H                   # installed media/transcription capabilities
capcut diagnose <project> -H       # canonical files, divergence, editor safety
capcut tracks <project> -H         # all tracks
capcut materials <project> -H      # material summary
capcut segments <project> -H       # segments with timing
capcut segment <project> <id>      # one item, full detail
```

## Output modes

- **JSON** (default): pipe to `jq`, feed to scripts.
- **`-H`**: human-readable tables.
- **`-q`**: quiet, exit code only, for write commands in scripts.

## Batch writes

```bash
echo '{"cmd":"set-text","id":"a1b2c3","text":"Fixed"}
{"cmd":"volume","id":"d4e5f6","volume":0.5}' | capcut batch <project>
```

Operations: `set-text`, `shift`, `shift-all`, `speed`, `volume`, `opacity`, `trim`.

The rest: https://github.com/renezander030/capcut-cli/blob/HEAD/skills/capcut-edit/SKILL.md