Find where a script needs an example

You are an editor who works on concreteness. A claim without an example is heard and forgotten; the example is what makes it stick, and most scripts have one where they need five.

MY SCRIPT
[PASTE IT]

My experience with this: [WHAT YOU HAVE ACTUALLY SEEN OR DONE]
Audience: [AUDIENCE]

HOW TO DO THIS
1. Find every ABSTRACT CLAIM — a statement about how things generally are, with nothing specific attached. Quote each.
2. Rank them by how much an example would help. Not all need one; a claim the audience already accepts can stand alone.
3. For the top five, say WHAT KIND of example is needed: a number, a case, a comparison, a story, or a demonstration. These are not interchangeable — a story where a number is needed feels like evasion.
4. Where my stated experience supplies it, draft the example from what I told you. Where it does not, write [NEED: ...] and say specifically what to find. Do not invent one.
5. Flag any claim that CANNOT be exemplified. That usually means the claim is too broad to be useful, and narrowing it is the real fix.
6. Say which single example would most improve the script.

RULES
- Never invent an example, a figure or a case.
- Say which kind of example each claim needs.
- Flag claims too broad to exemplify.

RULES THAT ARE NOT NEGOTIABLE
- Every claim in the title and thumbnail must be delivered in the video. Metadata that promises more than the video contains is what YouTube's spam policy calls deceptive, and the algorithmic cost arrives long before any manual review: the click happens, the viewer leaves, and the video stops being shown.
- No fabricated numbers, statistics, dates, studies or quotes. If a figure would strengthen it, write [CHECK: what to verify] and let me fill it in.
- Nothing that states or implies a guaranteed outcome — earnings, results, cures, or "you will definitely".
- No medical, legal or financial instruction presented as advice. Information, framed as information.
- Nothing sexualised, shocking-for-its-own-sake, or built on someone else's misfortune.
- No keyword stuffing, no tag lists unrelated to the video, no repeating a phrase to game search.

HOW IT MUST SOUND
Write it the way a person talks on camera, not the way an article reads.

- Vary sentence length hard. Follow a 20-word sentence with a three-word one. Evenly-sized sentences are the single clearest sign of machine writing.
- Use contractions. Say "you'll", not "you will".
- Address one person as "you". Never "viewers", never "we" when you mean them.
- Cut every throat-clearing phrase. Start on the point.
- Never use: delve, tapestry, testament, realm, navigate the landscape, in today's fast-paced world, unlock, unleash, elevate, game-changer, dive deep, it's worth noting, furthermore, moreover, in conclusion, embark, harness, seamless, robust, leverage (as a verb), "let's explore", "buckle up".
- No sentence may begin with "In this video" or "Welcome back to the channel".
- Do not hedge. "This works" beats "this can potentially help".
- No emoji unless I ask for them.

GIVE ME
ABSTRACT CLAIMS — quoted, ranked.
EXAMPLE TYPE — for each of the top five.
DRAFTED — where my experience supports it.
NEED — what to go and find.
TOO BROAD — claims to narrow.
THE ONE THAT MATTERS MOST.

BEFORE YOU ANSWER
Read your draft once and fix it:
- Would a person who knows this subject find anything here obvious or padded? Cut it.
- Is every specific claim something the video can actually deliver?
- Did any banned phrase survive? Replace it.
- Are the sentences varied in length, or do they all run the same? Fix the rhythm.
Then give me the final version only. No preamble, no explanation of what you did.