You drafted the script with AI, because that is the workflow. You edited it. You read it back and it seemed fine.
Then somebody watches thirty seconds and says it sounds like a robot wrote it.
This happens constantly. A creator on r/NewTubers posted a thread asking why his videos were getting no views at all, and the reply he got was four words long: sounds like an ai script. In another thread the note was gentler and just as vague — sounds like it is written by AI, I would spend time refining your future scripts and bringing a human element to it. In a third, someone put it as bluntly as it can be put: anything written by ChatGPT, at least at this point in time, sounds like a robot wrote it.
All three are correct. None of them are usable. Nobody says which sentence, which word, or what to do instead — and you cannot hear it yourself, because you already know what the script means. This article is the list nobody gives you.
What exactly makes a script sound machine-written?
A short, boring list of habits. It is not mysterious and it is not about intelligence. AI prose has a house style, and once you can name the parts you cannot unhear them.
- Stock openers. "In today's video." "Have you ever wondered." "You're not alone." "Let's dive in." These are the first four words of a million videos, and they signal a template before you have said anything.
- Written-register words. Delve. Utilize. Navigate. Landscape. Realm. Comprehensive. Testament. These are words people type and never say. One of them in a narration is a needle scratch.
- Hedge stacks. "Can often be somewhat difficult." Three hedges around a claim that has now said nothing. A narrator who knows the subject says the thing.
- Empty intensifiers. Absolutely crucial. Truly remarkable. Game-changing. Heat with no information — the written equivalent of a laugh track.
- The not-X-but-Y sentence. "It's not just about money, it's about freedom." The single most recognisable machine construction in circulation, and it usually arrives with a three-item list attached.
- The summary loop. Telling the viewer what the video will cover, then covering it, then recapping. Essays are built that way. Video punishes it, because you have just told someone to come back later.
- No contractions. "Do not." "It is." "You will." Formal on the page, unmistakably synthetic in a voiceover.
- No specifics. A paragraph with no number, no name, no place, no price. Machines generalise because they have nothing to remember.
That is eight, and any decent draft will contain all eight in the first three hundred words.
Why can't you hear it in your own script?
Because you read it and the audience hears it, and those are different senses.
On the page, a hedge looks like caution. A long even sentence looks like competence. A summary loop looks organised. Silent reading skips rhythm entirely — your eye takes the meaning and moves on, so a script can be fluent, correct, and completely lifeless without any of that registering.
Out loud, all of it lands. The hedge sounds like someone who has not done the thing. The even sentences sound like a machine metering out syllables. The summary loop sounds like a stall.
There is a second reason, and it is worse. You know what the script means before you read it, so you supply the emphasis, the pauses and the stance in your head. The viewer gets only what is on the page. You are the one person on earth who cannot hear your own draft cold.
The practical fix is to stop trying to hear it and start counting instead. Tells are countable. Rhythm is measurable. That takes the job away from your ear and hands it to a checklist.
What is the tell nobody mentions?
Sentence length. Specifically, the lack of variation in it.
Take any AI draft and count the words in each sentence. You will get something like 21, 19, 23, 18, 20, 22, 17, 24. Every sentence within a few words of every other one, for the whole script. It looks like nothing on the page. Read it aloud and it is a metronome.
A person writing at speed does not do that. They go long, then short, then a fragment. Then a one-word sentence. Then a long one again, because they got going. The unevenness is the sound of somebody thinking, and its absence is the sound of something generating.
This is why scripts that pass every other check still feel wrong. You removed "delve," you added contractions, you cut the intro — and the thing still marches. The rhythm was never touched.
The fix is mechanical and slightly uncomfortable: break sentences that do not need to be whole. Fragments are correct in narration. "Same dryer. Same clothes. Three times the money." is three sentences, eleven words, and no machine wrote it.
How do you fix a line without making it worse?
Four moves, in order. Most people try to fix robotic writing by adding personality, which usually means adding hype — and hype is just a louder robot.
- Cut the hedge and say the thing. "Rates can often vary significantly depending on your provider" becomes "your neighbour pays a different rate than you do." Shorter and braver.
- Add one specific. A number, a name, a place, a price. One per paragraph is enough. If you do not have the fact, do not invent it — leave a marked slot and go get it. Inventing a statistic to sound human is a far worse failure than sounding robotic.
- Break the rhythm. Split one long sentence into a long one and two short ones. Let one be a fragment.
- Take a side. The narrator is allowed an opinion. "This fee is legal and it is still a bad deal" is a human sentence because a machine hedging by default will not commit to it.
Notice what is not on the list: jokes, slang, exclamation marks, and "guys." Plain and specific beats loud every time, and a dry narrator who names a real number reads as more human than an excited one who does not.
How do you stop making the same tells next week?
You fix the drafting prompt, not the draft.
Once you have flagged a script, the same five or six words will account for most of the damage. In a typical draft, six words cover about seventy percent of the flagged lines. That is not a writing problem. That is a vocabulary the model reaches for by default, and you can take it away.
So the last output of any audit should be a ban list: delve, crucial, moreover, navigate, landscape, it is important to note. Paste that straight into the prompt you draft with as a hard rule, along with a rhythm instruction — vary sentence length, use fragments, never open with "in today's video."
The next script arrives already thirty points cleaner, and you spend your editing time on the lines that are actually about the content. That compounding is the whole reason to audit at all; fixing one script is worth an hour, fixing your prompt is worth every script after it.
What does the real output look like?
Here is the actual output from the sample run — a faceless home-money channel, one AI-drafted opening, 300 words:
TELLS FOUND 19 DENSITY 1 every 16 words CONTRACTIONS 2 of 31 chances (6%) SPECIFICS 0 numbers, 0 names, 0 places 1 Latinate swap 5 "delve into the fascinating world" 2 Empty intensifier 4 "absolutely crucial" 3 Hedge stack 3 "can often be somewhat difficult" 4 Stock opener 2 "In today's video, we're going to"
Not "it sounds like AI" — nineteen specific words, ranked by how often this writer reaches for them.
Sentence lengths: 21, 19, 23, 18, 20, 22, 17, 24, 19, 21, 20, 28 Every sentence is the same length. A person goes long, then short, then two words.
The tell that survives every other edit, because it is invisible until the moment you record.
"Your power bill went up again. Mine did too. Three hundred and twelve dollars last month, for a house I'm barely in. Here's the part nobody tells you. You're not paying for how much power you use. Not really. You're paying for when. Run your dryer at six in the evening and it can cost three times what it costs at eleven at night. Same dryer. Same clothes. Three times the money."
Same facts, same narrator. Sentence lengths now 6, 4, 13, 6, 12, 3, 4, 18 — and the narrator pays the bill in the first eight words.
It closes with the six words to ban in the drafting prompt, which covered 71% of the flagged lines in this script alone.
How do you run it yourself?
You paste one prompt into Claude Code and it builds the tool for you. It is a dark dashboard, pre-filled with the sample above, so it works on the first run.
It has a Settings panel for your own API key, so you can run it on every script before you record — and on the last script you published, which is usually where the first uncomfortable surprise is.
Grab it below. Drop your email and the prompt is on the very next page, free. Paste it in, then run it on your own draft.
Can you turn this into a side hustle?
Yes, and it is a service business with almost no setup. The tool does the production; you do the selling and the quality check.
It works like this: local businesses pay for Paste your AI-drafted script. Get a robot score, every line that gives it away with the exact tell named, and a human rewrite of each one — in your narrator's voice, before you record. all the time. You take the job, let the tool do the heavy lift, review it, and hand it over. Typical pricing is $500 a month per client.
The best part is the cost to start: a free prompt — it pays for itself on the first job. The tool does the heavy lifting in minutes, so your margin is high and you can take on more clients without more hours. To get your first client, reach out to a few local businesses you already know. Do one for free, show them the result, and ask who else needs it.
FAQ
Will it rewrite my whole script for me?
It rewrites every line it flags, and rebuilds the opening end to end so you can see the before and after side by side. The rest of the script comes back with flags and rewrites line by line, so you keep control of what you accept.
Does it change what my script says?
No. It changes voice, not content. Every fact from your draft survives, and it is explicitly told never to invent a number, a study or a personal story to make a line sound human — if a specific would help, it leaves a marked slot for you to fill.
Is this an AI detector?
No, and that is the point. Detectors give you a percentage and no instructions. This names the specific tell in a specific line and writes the replacement, which is the only part that changes your video.
I'm not a native English speaker. Does that help or hurt?
It helps a lot. The tells are a fixed list, so the tool catches formal or textbook phrasing that reads as machine-written, and gives you the natural spoken version of the same line — which is exactly the part that is hardest to hear from outside the language.
Can I reuse it on every script?
That is the point. Enter your API key once and run it on each draft before you record. It also gives you a ban list for your drafting prompt, so the scripts arrive cleaner over time.