editly-render
/editly-render
Render a video from a declarative editly JSON spec (clips, transitions, titles, audio mix). Use when the user says "render this editly spec", "compose this slideshow", "make a video from this JSON", "editly render". Validates the spec, runs editly headlessly, and reports the deliverable. Editly must be installed via `deps-setup` (npm-global).
- Author
- danielrosehill ↗
- Repository
- claude-video-editor-plugin ↗
- Licence
- MIT
- Last repository change
- 03.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 03.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Render a video from a declarative editly JSON spec (clips, transitions, titles, audio mix). Use when the user says "render this editly spec", "compose this slideshow", "make a video from this JSON", "editly render". Validates the spec, runs editly headlessly, and reports the deliverable. Editly must be installed via `deps-setup` (npm-global).
Triggers from the description
Original author description
Render a video from a declarative editly JSON spec (clips, transitions, titles, audio mix). Use when the user says "render this editly spec", "compose this slideshow", "make a video from this JSON", "editly render". Validates the spec, runs editly headlessly, and reports the deliverable. Editly must be installed via `deps-setup` (npm-global).
How it works
- Procedure
- Notes
SKILL.md preview
---
name: editly-render
description: Render a video from a declarative editly JSON spec (clips, transitions, titles, audio mix). Use when the user says "render this editly spec", "compose this slideshow", "make a video from this JSON", "editly render". Validates the spec, runs editly headlessly, and reports the deliverable. Editly must be installed via `deps-setup` (npm-global).
disable-model-invocation: false
allowed-tools: Bash(test *), Bash(ls *), Bash(mkdir *), Bash(jq *), Bash(basename *), Bash(dirname *), Bash(realpath *), Bash(command *), Bash(editly *), Bash(node *), Bash(ffprobe *), Read, Write
---
# Editly Render
Run [`editly`](https://github.com/mifi/editly) on a JSON spec to compose a video. Editly is a declarative slideshow / montage tool — clips, titles, transitions, audio mix all described as JSON.
## Procedure
### 1. Verify editly
```bash
command -v editly >/dev/null || { echo "editly not installed. Run deps-setup and select editly (npm-global, requires Cairo + ffmpeg)."; exit 1; }
editly --version
```
### 2. Inputs
| Field | Default |
|-------|---------|
| Spec | required: path to `.json` or `.json5` editly config |
| Output | default: derived from spec filename, `.mp4` |
| Fast mode | `no` (full quality). `yes` adds `--fast` for quick previews |
| Audio normalize | `yes` (editly's `--audio-norm`) |
### 3. Validate the spec
```bash
SPEC="$(realpath "$INPUT")"
test -f "$SPEC" || { echo "Spec not found: $SPEC"; exit 1; }
jq -e . "$SPEC" >/dev/null 2>&1 || {
# editly accepts json5; only fail if the file is also not valid json5
node -e "require('json5').parse(require('fs').readFileSync('$SPEC','utf8'))" 2>/dev/null \
|| { echo "Spec is neither valid JSON nor JSON5."; exit 1; }
}
```
Sanity-check required top-level fields:
```bash
jq -e '.outPath // .clips' "$SPEC" >/dev/null || echo "Warning: spec has no .clips — editly will likely error."
```
Resolve the output path. If `outPath` is set in the spec, use it; otherwise pass `--out`.
### 4. Pre-flight: source files exist
For each clip/audio reference inside `clips[].layers[]` and the top-level `audioFilePath`, verify the file exists relative to the spec's directory. List any missing files and abort before invoking editly.
```bash
SPEC_DIR="$(dirname "$SPEC")"
MISSING=$(jq -r '
[(.clips // [])[] | (.layers // [])[] | (.path // empty)] +
[(.audioFilePath // empty)] | .[]
' "$SPEC" | while read -r p; do
[ -z "$p" ] && continue
case "$p" in
/*) f="$p" ;;
*) f="$SPEC_DIR/$p" ;;
esac
[ -f "$f" ] || echo "$p"
done)
[ -n "$MISSING" ] && { echo "Missing source files:"; echo "$MISSING"; exit 1; }
```
### 5. Run editly
```bash
ARGS=( "$SPEC" )
[ -n "$OUT" ] && ARGS+=( --out "$OUT" )
[ "$FAST" = "yes" ] && ARGS+=( --fast )
[ "$AUDIO_NORM" = "yes" ] && ARGS+=( --audio-norm )
editly "${ARGS[@]}"
```
Stream editly's progress output live.
### 6. Verify
```bash
ffprobe -v error -show_entries format=duration,size -of default=nw=1 "$OUT"
```
Print: output path, duration, size, container.
### 7. Confirm
Suggest follow-ups: `audio-analysis` (loudness check), `transcode` (re-encode to a final delivery profile — editly's default output is software h264), `burn-graphics` (add overlays editly can't compose).
## Notes
- Editly's defaults produce software-encoded h264 — for hardware-encoded final deliverables, run `transcode` or `render-with-profile` on the editly output.
- The `--fast` flag drops resolution and quality; useful for iterating on a spec, never for final delivery.
- Cairo is a hard dependency on Linux for editly's text rendering — if rendering fails with a Cairo error, the user needs `libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev` (Debian/Ubuntu) before reinstalling editly.
- For non-declarative ("describe what to keep") cuts, use `agentic-edit` instead.
Versions
The database has no other skills named editly-render.
Database snapshot: 13.11.2026 · package version 2c47fa9b979b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100editor
Composition and render craft — assembles scenario.json plus asset-manifest.json into a HyperFrames HTML composition and renders the mp4. Owns timing, transitions, captions, audio mix and ducking, the green zone, the render pipeline, and VO sync. Generates no media of its own.… - 100editor
Composition and render craft — assembles scenario.json plus asset-manifest.json into a HyperFrames HTML composition and renders the mp4. Owns timing, transitions, captions, audio mix and ducking, the green zone, the render pipeline, and VO sync. Generates no media of its own.… - 100render-with-profile
Render one or more video files using a previously saved render profile. Use when the user says "render these clips at YouTube 1080p", "apply my <profile> preset", "batch render this folder with <profile>", or similar. Reads render-profiles.json + system-profile.json; writes… - 100video-edit
Plan, cut, caption, animate and render video with code. Use for any request to edit footage or make a video (short-form Reels, TikTok, Shorts, talking head, product demo, tutorial, explainer), to write an edit plan or EDL, choose cuts, B-roll or transitions, make captions or… - 100render-from-library
Assemble a single video from a folder of clips — concat in a chosen order, optionally with crossfade transitions, normalized to a target resolution/fps. Use when the user says "stitch this folder into one video", "render-from-library", "concat the clips in folder X", "make a… - 100render-pipeline
Author a video as a single HTML composition and render it deterministically to MP4. Use whenever the deliverable is a video, animation, motion graphic or overlay: it defines the timing attributes, the paused-timeline contract, the render commands, and the failure modes.