capcut-cli
Enables programmatic video editing workflows without CapCut API access, allowing teams to automate subtitle insertion, timing adjustments, and long-form-to-s…
CLI to edit CapCut and JianYing projects — subtitles, timing, speed, volume, templates, cut long-form to shorts. No API needed, reads draft_content.json directly.
- Automate subtitle addition to CapCut projects without opening the desktop application.
- Extract and batch-edit video timing and speed settings across multiple project files.
- Convert long-form videos into short-form clips by cutting segments via command line.
Enables programmatic video editing workflows without CapCut API access, allowing teams to automate subtitle insertion, timing adjustments, and long-form-to-shorts conversion at scale.
Content production teams automating video post-processing pipelines and bulk editing tasks.
https://github.com/renezander030/capcut-cli
By renezander030
How to Get It
claude plugins install renezander030/capcut-cli
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me automate subtitle addition to CapCut projects without opening the desktop application
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Reddit
- CapCut Version Guard - Block unwanted auto-updates and keep your preferred versi — Reddit · 3 pts
- Looking for CapCut alternative or CLI tool for batch video exports + styled lyri — Reddit · 2 pts
- Still editing CapCut subtitles one at a time? Try my CLI. — Reddit
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 223 GitHub stars; 7 contributors; last commit 1d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 223 GitHub stars; 7 contributors; last commit 1d ago; license MIT.