JasonColapietro/suede-creator-skills / skills/suede-video
suede-video
VerifiedPlan or produce marketing video with scripts, storyboards, shot and asset lists, consent-aware AI or avatar choices, programmatic rendering, edit decisions, pacing, export specs, and video-search metadata. Use when asked to "turn this demo into a short video" or build a repeatable production pipeline. NOT FOR: social calendars (use suede-social), clip-to-guide bridges (use suede-clip-to-guide), paid ad concepts (use suede-ad-creative), still images (use suede-image), or unapproved publishing.
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 20.6 KB |
| agents/openai.yaml | config | 545 B |
| evals/evals.json | config | 11.0 KB |
| references/ai-video-prompting.md | markdown | 5.5 KB |
| references/edit-anatomy.md | markdown | 7.1 KB |
| references/programmatic-renderers.md | markdown | 2.7 KB |
| references/worked-handoff.md | markdown | 1.6 KB |
references/edit-anatomy.md
View on GitHub# Reverse-Engineering an Edit (The Beat Sheet)
A reference video's outcome may reflect its edit, footage, audience,
distribution, topic, or account history. This reference isolates the editing
choices into a **reusable edit spec** so they can be tested on original footage
without claiming the edit caused the observed performance.
This is the tool-agnostic half of "copy any viral edit": the *decomposition*. The generation is whatever you edit with afterward: CapCut, Premiere, Remotion/Hyperframes, or an AI restyle tool. The spec is the deliverable.
## When to use it
- A competitor's or creator's edit keeps stopping your scroll and you want to understand *why* and replicate the technique
- You have raw footage (a talking-head clip, a demo) and a reference edit whose style you want to match
- You're briefing an editor or a template and need the edit decisions written down, not vibes
Don't use it to copy someone's actual creative: this extracts the *editing grammar* (structure, rhythm, caption treatment), not the script, footage, or brand. Same rule as mining organic content for vocabulary in the hook system: take the technique, never the creative.
## Step 1: Pull the reference so you can actually read the edit
You cannot decompose an edit from a description alone. First discover whether a
currently callable, authorized media viewer, local-file inspector, or browser
can expose the frames and timing.
- If available, inspect the actual media and sample frames at cut points.
- If only a public post is available, use an authorized browser or source reader
within the platform's terms.
- If no tool is available, ask the user for the media file, screenshots, or a
timecoded export and give them a manual frame-sampling checklist.
- Never claim to have seen frames that were not actually rendered or supplied.
Note the total duration and roughly how many cuts there are before you start: cuts-per-second is the single most telling number about an edit's energy.
## Step 2: Extract the anatomy, beat by beat
Walk the reference from 0:00 and log every editing decision. The dimensions that define a short-form edit:
| Dimension | What to read off the reference |
|---|---|
| **Shot & framing** | Talking head / screen recording / b-roll / text card; close-up vs. wide; headroom, rule-of-thirds, or dead-center |
| **Cut rhythm** | Where each cut lands and how fast (cuts-per-second); is it on the beat, on the word, or on the breath? |
| **On-screen text** | The words, when each appears/disappears, and *where* on the frame (top-third caption vs. big centered statement) |
| **Caption style** | Font, weight, color, outline/box, and animation (word-by-word pop, karaoke highlight, whole-line) |
| **Motion** | Punch-ins / zoom pushes, shakes, whip-transitions, speed ramps, where and how aggressive |
| **B-roll & overlays** | Cutaways, stickers, arrows, emoji, screenshots, meme inserts: what's laid over the base footage and when |
| **Sound design** | Music choice and where it hits, SFX (whooshes, dings, risers), and deliberate silence before a beat |
| **Hook (first 2s)** | The single most-copied element: what's on screen and said in the opening two seconds, before anyone's committed |
| **Pacing curve** | Does it stay frantic, or fast-hook → slower-body → fast-CTA? Map the energy over the runtime |
Read the *pattern*, not just the instances: "a hard cut + punch-in on every new sentence," "caption is one word at a time, yellow, karaoke-highlighted, bottom third," "a whoosh SFX on every scene change." Patterns are what make an edit replicable; a list of 40 individual cuts is not.
## Step 3: Write the beat sheet
Two artifacts: a per-beat table and a short style summary.
**The beat sheet**: one row per beat (a beat = a cut or a distinct edit event):
```
| Beat | Time | Shot | On-screen text | Caption style | Transition / motion | Audio |
|------|-----------|-----------------|-----------------------|----------------------|-----------------------|------------------|
| 1 | 0:00–0:02 | CU talking head | "STOP doing this" | word-pop, yellow, ctr| hard in, slow push | music in + riser |
| 2 | 0:02–0:04 | screen record | (caption only) | karaoke, white, btm | hard cut + whoosh | click SFX |
| … | | | | | | |
```
**The style summary**: the 3–5 *signature moves* that make this edit recognizable, stated so they're reusable:
- e.g. "Every sentence gets a hard cut + a 5% punch-in." / "Captions are one word at a time, bottom-third, karaoke-highlighted." / "A whoosh SFX on every cut; music drops out for 0.5s before the CTA." / "The hook is a bold centered statement on frame 1, no logo."
The signature moves are the real deliverable: someone can apply those five rules to any footage and get the style. The table is the detailed backup.
## Step 4: Review once, then execute
Show the beat sheet before anyone edits anything: the same review-once gate as the ad-creative creative review page. The reviewer checks two things:
- **The on-screen text says what you want** (mapped to your message, not the reference's)
- **The scene changes land where you want them** (your footage's beats, not a blind copy of the reference's timing)
Approve, then execute the spec with your footage:
- **Remotion / Hyperframes**: when you want the edit templated and data-driven (see the programmatic-video section in SKILL.md); the beat sheet *is* the composition spec.
- **CapCut / Premiere / an editor**: hand off the beat sheet + style summary as the brief.
- **An AI restyle tool**: feed the style summary as the target style.
## Originality guardrail
You are copying the *edit*, not the content. The beat sheet describes technique (cut rhythm, caption treatment, motion, sound design) applied to **your** footage and **your** message. General editing techniques and style cues are usually reusable (U.S. copyright protects expression, not procedures or methods, 17 U.S.C. §102(b)), but the reference's specific creative expression is not, and closely reproducing a finished video's exact selection and arrangement of choices can still create risk. So copy the grammar, not the finished work: use your own footage, message, script, voiceover, licensed music/SFX/samples, and brand elements. If the reference's "style" is really a specific bit or sketch, that's their creative, draw inspiration, don't reproduce it.
## Common mistakes
- **Describing instead of reading**: you cannot extract caption style or cut
timing from a transcript alone; inspect supplied or actually rendered frames.
- **Logging instances, not patterns**: 40 cut timestamps isn't a spec; "hard cut + punch-in per sentence" is.
- **Copying the reference's timing onto different footage**: beats land on *your* words and *your* cuts; the reference gives you the grammar, not the calendar.
- **Skipping the hook**: the first 2 seconds carry most of the retention; decode them in the most detail.
- **Reproducing the creative**: matching the edit is fine; re-shooting their exact bit, script, or using their footage/music/SFX is not.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |