agentleFS
eliftforlifeeliftforlife/claude-video-editing-skills/interview-shot-sheet/SKILL.md

interview-shot-sheet

Skill4 starsChanged 33 days agoMITView on GitHub

Interview the creator about a video idea until the best story is found, then write a bullet-point shot sheet they can read off a second phone while recording. Use when someone asks for help planning, scripting or finding the angle for a YouTube video.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask questions in rounds of 5–7, short enough to answer by voice-to-text.

    line 12
  2. Distinctive:

    Contradictions: if two answers disagree, ask.

    line 26
  3. Very specific:

    Never invent numbers, features, quotes or results.

    line 28
  4. Distinctive:

    Only use a format the creator has proof for.

    line 37
  5. Distinctive:

    Keep lines short: they'll read it off a second phone mid-take.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview + shot sheet

Your job is to find the story before anything gets recorded. Talking-head videos live or die on the story and the proof, not the editing.

1. Interview

Ask questions in rounds of 5–7, short enough to answer by voice-to-text. Ramble-y answers are fine; you're mining for details.

Round 1 covers the basics:

  • Before: how did they do this before? How long did it take, what did it cost?
  • The switch: what was the moment they changed? (This is usually the hook.)
  • Now: real numbers. Time, money, results.
  • Worst moment: what went wrong, what almost made them quit?
  • Wow moment: the first time it actually worked.
  • Limits: what still needs a human? Admitting limits makes the rest believable.
  • Viewer: who is this for, and what will they want to know?

Round 2 is follow-ups on whatever has the best story. Chase:

  • Proof: screenshots, receipts, archive photos, numbers on screen
  • Specifics: "about 10 hours" beats "a long time"
  • Contradictions: if two answers disagree, ask. Never guess a number.

Never invent numbers, features, quotes or results. If a fact is missing, leave a [blank] for them to say out loud.

2. Title first

Pick the title before the shot sheet. Formats that work for "here's what I learned" videos:

  • If I Started [X] in [year], I'd Do This
  • I [did hard thing]. Here's What Happened
  • [Big number] [unit] → [small number] (my exact setup)

Only use a format the creator has proof for.

3. Shot sheet

Bullet points, not a script. One numbered take per idea, 1–2 bullets each, so every take is 1–2 minutes. The editor can rearrange takes later, so order matters less than coverage.

1. HOOK
- "Everything in this video was ..." (the result first)
- "If I started ..., here's exactly what I'd do."

2. WHERE I STARTED
- old way + real number

3. STEP 1: ...
...

N. OUTRO
- callback to the title + what's next

At the bottom, list the B-roll to screen-record today (apps, uploads, before/after).

Keep lines short: they'll read it off a second phone mid-take.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.