← ClaudeAtlas

shorts-editorlisted

Cut a customer's long video into 9:16 shorts and act on review notes — pick the shorts from the transcript, write shorts.json, snap, frame, check the contact sheets, render drafts, and turn each review comment (with its time range) into an edit of shorts.json or framing overrides, then re-render and reply. Use when asked to make shorts from footage, a podcast, an interview, a film or a long video, or to apply review comments on such shorts. Never approves or releases a short.
tamtree-ai/stick-stage · ★ 2 · Code & Development · score 68
Install: claude install-skill tamtree-ai/stick-stage
# Shorts editor You are the editor's hands for the shorts service. The pipeline is `packages/shorts` (Python) plus the `ShortFromFootage` composition (`src/app/shorts/`). Read `packages/shorts/README.md` for the commands. Every step's output is a JSON file in one work dir, and you edit those files directly. ## Picking shorts (writing shorts.json) Run `uv run shorts transcript --work $W` and read all of it before choosing. A short is good when: 1. **It is a complete thought.** It has a setup and a payoff. Never end before the explanation; that is the top complaint about AI clippers. 2. **It works cold.** No "as I said earlier" or names the viewer hasn't met, unless the clip itself introduces them. 3. **It hooks in the first 2 s.** Either the main segment opens strong, or add a **teaser** segment: 2–5 s of the payoff line, played first, then the main segment from the start. 4. **20–60 s in total**, teaser included. If the moment is longer, split it into several `main` segments that skip the slack. Each jump is a cut with an audio fade. 5. **Not a repeat.** Shorts from the same video shouldn't share their payoff. For each short write `title` (≤ 6 words, on screen after the teaser), `hook` (on-screen text over the opening, ≤ 8 words, a question or a claim), `closing` (the end card line: the moral, the fact or the CTA), and `why` (two plain sentences for the reviewer: what the viewer gets and why it works cold). Then run `shorts snap` and fix every `!` it prints.