trial-reels — Claude Code skill: reels and installation
This Claude Code skill turns one clip into three reels with distinct visual treatments. It runs with /trial-reels or a request for alternate versions of a vertical clip.
MIT ★ 94 updated 2026-10-30
/plugin marketplace add artemnovitckii/claude-editing-skills
/plugin install editing-skills@claude-editing-skillsWhat trial-reels does
The skill transcribes a video segment, prepares three visual treatments, and builds each as an MP4. One uses a title and karaoke-style captions, another adds a post header with the speaker’s avatar and name, and the third frames the clip with a stat drawn from its content. A JSON spec holds the video paths and design text.
The word extraction script runs first; build.py then creates the videos and review sheets. After checking the sheets, the skill hands over the three file paths with a short note about what each version tests. Transcription requires GROQ_API_KEY; the setup also needs ffmpeg, Node, and Python 3. If the virtual environment is missing, setup.sh creates it.
What it helps with
- create three visual treatments from one clip
- prepare reel variations for a side-by-side test
- build MP4 versions with sheets for review
Example prompts for the agent
- Create three reel versions from
my-reel.mp4with/trial-reels. - Make distinct visual treatments for this vertical clip.
- Build three test versions of the opening segment.
How to install trial-reels
1Plugin marketplace
/plugin marketplace add artemnovitckii/claude-editing-skills/plugin install editing-skills@claude-editing-skillsThis installs the whole editing-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add artemnovitckii/claude-editing-skills --skill trial-reels -a claude-code3Manually: put the files in place
~/.claude/skills/trial-reels/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/trial-reels/
1Skills CLI (Vercel)
npx skills add artemnovitckii/claude-editing-skills --skill trial-reels -a codex2Manually: put the files in place
.agents/skills/trial-reels/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add artemnovitckii/claude-editing-skills --skill trial-reels -a cursor2Manually: put the files in place
.cursor/skills/trial-reels/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install artemnovitckii/claude-editing-skills skills/trial-reels2Manually: put the files in place
.github/skills/trial-reels/SKILL.md1Skills CLI (Vercel)
npx skills add artemnovitckii/claude-editing-skills --skill trial-reels -a gemini-cli2Platform CLI
gemini skills install https://github.com/artemnovitckii/claude-editing-skills --path skills/trial-reelsManually: put the files in place
.devin/skills/trial-reels/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about trial-reels
How do I install trial-reels in Claude Code?
Add the marketplace with /plugin marketplace add artemnovitckii/claude-editing-skills, then install the skill with /plugin install editing-skills@claude-editing-skills.
What does trial-reels do?
It creates three visually distinct edits from one clip, then builds a separate MP4 and review sheet for each version.
What does trial-reels need to run?
Transcription needs GROQ_API_KEY. The setup also requires ffmpeg, Node, and Python 3.
Source text
SKILL.md · MIT
---
name: trial-reels
description: Turns one talking-head clip into 3 visually distinct reels to post as Instagram trial reels, so you can see which look wins. Version 1 has a big yellow title and karaoke captions, version 2 a white post-card header with punch-in zooms and bold uppercase captions, and version 3 a dark grid backdrop with a pixel-font stat and the clip in an orange frame. Use when the user runs /trial-reels or asks for trial reel versions, variations or A/B looks of a 9:16 clip.
---
# /trial-reels
```
1 TITLE + KARAOKE 2 POST HEADER 3 PIXEL FRAME
┌──────────────┐ ┌──────────────┐ ┌──────────────┐
│ CAROUSELS ARE│ │(o) Name │ │ 2× │
│ INSTAGRAM │ │ The hook as a│ │ the views of │
│ CHEAT CODE │ │ headline │ │ ┌──────────┐ │
│ (face) │ │ (face, zooms│ │ │● REC face│ │
│ grey→white │ │ CHEAT CODE │ │ │ pixel cap│ │
└──────────────┘ └──────────────┘ └──────────────┘
```
## First use
This skill's folder is the "Base directory" Claude Code shows when it loads it.
```bash
SKILL_DIR="<base directory of this skill>" # the path Claude Code printed as "Base directory for this skill"
KIT=$(python3 -c 'import os,sys;print(os.path.realpath(os.path.join(sys.argv[1],"..","..","kit")))' "$SKILL_DIR")
PY="$KIT/.venv/bin/python"; [ -x "$PY" ] || bash "$KIT/setup.sh"
```
`GROQ_API_KEY` must be set to transcribe. Needs ffmpeg and Node.
## Steps
1. **Clip.** The user's finished reel or its hook. Whole clips work. The hook (first 5 to 10 s) is the usual test.
2. **Words.** Run `"$PY" "$KIT/reel.py" words <video>` and read the hook. Each sentence ends with `[ends …]`: use the last one you keep as `end`.
3. **Write three different packagings of the same idea.** Each version is a different promise, not just a different font:
- **v1 title**: the claim, 3 lines, with the 1 or 2 key lines bigger (`*line*`).
- **v2 headline**: the hook rewritten as a post headline ("The Instagram cheat code not many people know about"), plus the speaker's avatar and name. `keys` are the caption words to turn yellow (the punch-ins land on them).
- **v3 stat**: the single number or comparison in the clip ("2×", "10K", "$0") plus a 3 to 5 word line.
4. **Spec.** Write `<clip>.trial-reels.json` (below). Paths in a spec are relative to the spec file.
5. **Build.** Run `"$PY" "$SKILL_DIR/build.py" <spec.json>`. It writes `<out>-1.mp4`, `<out>-2.mp4` and `<out>-3.mp4`, each with a sheet.
6. **Check.** Look at all three sheets:
- The titles clear the top 220 px.
- The captions sit under the face, not on it.
- The three versions look clearly different at a glance.
7. **Hand over** the three paths with one line each on what the version tests.
## Spec
```json
{
"video": "my-reel.mp4", "start": 0, "end": 6.95,
"v1": {"title": ["carousels are an", "*instagram*", "*cheat code*"]},
"v2": {"avatar": "me.jpg", "name": "Your Name", "sub": "Instagram growth",
"headline": "The Instagram cheat code not many people know about",
"keys": ["cheat", "code", "twice", "views"], "punches": ["cheat", "twice"]},
"v3": {"stat": "2×", "line": "the views of reels", "pulse_at": "twice"}
}
```
Optional fields:
- **`caption_top`** per version: 1400 for v1, 1260 for v2, 1330 for v3 by default.
- **`punches`**: defaults to the key words, at least 1.5 s apart.
## Taste
- Same clip, same words, three different first impressions. Change the promise, not just the paint.
- No invented numbers. The v3 stat must be something said in the clip.
- Post all three as trial reels on the same day and keep the one with the best 3-second hold.
© Artem Novitckii · MIT · artemnovitckii/claude-editing-skills