Agent skill · Media & Video

wjs-editing-multicam

Use when the user has 2+ recordings of the same event (each with a `.sync.json` sidecar from wjs-syncing-multicam) and wants them combined into a single MP4 — auto-switching between cams second-by-second on audio energy, with optional picture-in-picture inset. Triggers — "auto-edit multicam", "做个剪辑", "切几个机位", "把这几个视频合成一个", "combine these angles", "PiP overlay".

jianshuogithub.com/jianshuoGitHub ↗
claude-codecodexMIT
Install
npx skills add jianshuo/claude-skills --skill wjs-editing-multicam --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 12 KB
Bundled scripts: none
Path: wjs-editing-multicam/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 112
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# wjs-editing-multicam Combine N synced camera angles into a single rendered MP4. Decisions are audio-energy-driven only — the cam with the loudest mic each second wins. Output is hard cuts (or hard cuts plus a corner PiP). ## Setup & commands The implementation lives in the open-source **`polysync`** pip package (<https://pypi.org/project/polysync/> · <https://github.com/jianshuo/polysync>) — this skill no longer ships its own scripts. Install it, then drive it via its CLI: ```bash python3 -m pip install -U polysync # needs ffmpeg/ffprobe on PATH polysync edit CAM_A CAM_B CAM_C --out edl.json # build the decision list polysync render-cuts edl.json --out out.mp4 # hard cuts polysync render-pip edl.json --out out.mp4 --pip bottom-right # cuts + corner inset ``` `edit` and the renderers read each input's `.sync.json` automatically. Sync first with **wjs-syncing-multicam** (`polysync sync`) if the sidecars don't exist yet. Render flags for raw camera footage (see **Preflight** below for when to use each): ```bash # Sony S-Log3 footage, shot vertical, FX6 cams turned on their side, for 小红书: polysync render-cuts edl.json --out out.mp4 \ --log slog3 \ # S-Log3/S-Gamut3.Cine -> Rec.709 gr

What's inside
Steps it walks through
  1. Setup & commands
  2. Preflight — ALWAYS check raw footage before rendering (hard-won)
  3. Editing quality — when polysync edit isn't enough
  4. What this skill IS — and IS NOT
  5. REQUIRED INPUT
  6. When NOT to use
  7. Pipeline
  8. EDL schema (edl.json)
  9. Render
  10. Brainstorm before running
  11. File layout
  12. Common pitfalls
Commands it runs
python3 -m pip install -U polysync      # needs ffmpeg/ffprobe on PATH
polysync edit        CAM_A CAM_B CAM_C --out edl.json   # build the decision list
polysync render-cuts edl.json --out out.mp4             # hard cuts
polysync render-pip  edl.json --out out.mp4 --pip bottom-right   # cuts + corner inset
Sony S-Log3 footage, shot vertical, FX6 cams turned on their side, for 小红书:
polysync render-cuts edl.json --out out.mp4 \
More from claude-skills
All skills →
About this skill
What does the wjs-editing-multicam skill do?

Use when the user has 2+ recordings of the same event (each with a `.sync.json` sidecar from wjs-syncing-multicam) and wants them combined into a single MP4 — auto-switching between cams second-by-second on audio energy, with optional picture-in-picture inset. Triggers — "auto-edit multicam", "做个剪辑", "切几个机位", "把这几个视频合成一个", "combine these angles", "PiP overlay".

How do I install it?

Run `npx skills add jianshuo/claude-skills --skill wjs-editing-multicam --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jianshuo/claude-skills, a repository with 112 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going