YouTube

Verified against ChatGPT · 2026-07-20

Outline a how-to script paced for people actually following along, not just watching

Structures a tutorial script around the moments a real viewer pauses to act, not just the moments a narrator finishes explaining — the specific gap where most instructional videos lose people who are trying to follow along in real time.

ChatGPTClaudeGemini5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are outlining a how-to or tutorial video script paced for a viewer who is actually trying to follow along and do the thing, not just watch passively. A tutorial script that reads well as narration can still fail its actual audience if it never gives someone doing the task in real time a moment to catch up, which is a different failure than a boring or unclear explanation.

TASK BEING TAUGHT
Replacing a bicycle chain and adjusting the derailleur afterward

VIEWER SKILL LEVEL
Complete beginner — has never used bike tools before, may not own a chain tool yet

MATERIALS OR TOOLS REQUIRED
New chain sized to the bike, a chain tool, a small screwdriver, gloves recommended

KNOWN TRICKY STEPS
Getting the new chain length exactly right (too many or too few links is the most common beginner mistake), and reconnecting the chain without the connector pin popping out under tension

TARGET LENGTH
10-13 minutes

OUTLINE RULES
Open by stating the full materials or tools list and the total time commitment before any instruction begins — a viewer deciding whether to follow along right now needs that information upfront, not discovered piecemeal as each tool is introduced mid-step, which forces someone already mid-task to pause and go find something they didn't know they'd need. Break the task into discrete numbered steps matched to natural stopping points in the actual physical or digital process, not to arbitrary time chunks — a step boundary should fall where a real person doing this would naturally look up from the task to check they're still on track, not wherever happens to be a clean two-minute mark. For any step flagged as tricky, slow the pacing specifically there: state the common mistake explicitly before it happens, not only how to do it correctly, since a viewer who doesn't know a mistake is common won't know to be careful at the one point where care actually matters. Build in an explicit verbal checkpoint after any step a viewer would need real time to complete alongside the video, not just watch — "pause here if you need to, this next part assumes the last step is done" — rather than assuming a viewer will manage their own pacing by scrubbing the video themselves, since most viewers won't. State results or symptoms of getting a step wrong, where relevant, so a viewer who's fallen behind or made a mistake has a way to self-diagnose rather than only discovering something's wrong at the very end. Do not front- or back-load all the tricky content — if there are multiple genuinely hard steps, each one gets its own slowdown and explicit mistake-warning in place, not just the first one encountered.

OUTPUT FORMAT
1. Materials/tools and total time, stated as a single upfront block.
2. Numbered steps, each with an estimated timestamp, the instruction, and — for any step matching a tricky step provided — the specific common mistake called out before the instruction.
3. Explicit checkpoint lines marked clearly, placed after any step requiring real hands-on time.
4. A closing troubleshooting note listing symptoms of the most likely things to go wrong and what they indicate.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Separating "a script that reads clearly" from "a script paced for someone actually doing the task in real time" names a real and specific gap: a narrator can finish explaining a step in fifteen seconds while the physical or digital action it describes takes a viewer two full minutes to actually complete, and a script written only for narrative clarity has no mechanism to account for that mismatch — it just keeps talking, and a viewer following along either falls behind or gives up and switches to passive watching, defeating the tutorial's actual purpose. Requiring the materials and time commitment upfront, rather than introduced tool-by-tool as each is needed, targets a specific and common frustration in tutorial content: a viewer who is already elbow-deep in step four discovering they need a tool they don't own has to pause, go find or buy it, and return, which is a much worse experience than knowing that requirement before starting at all and deciding then whether to proceed. Slowing down specifically at flagged tricky steps, and stating the common mistake before the instruction rather than only the correct method, matters because knowing a step is difficult changes how carefully a person performs it — a viewer told nothing extra about a genuinely error-prone step approaches it with the same attention as an easy one, and the mistake the flag was meant to prevent happens anyway, silently, with the viewer only discovering something's wrong steps later when the consequence surfaces. The explicit checkpoint instruction addresses the single biggest structural difference between a tutorial and ordinary narrative video: video plays at a fixed pace and hands do not, so any step requiring real manual time needs an explicit, stated permission to pause — without it, most viewers won't self-manage pausing well, either rushing to keep up with narration that's already moved on or, less often, pausing so much they lose the thread of what comes next. The closing troubleshooting note, tied to specific symptoms rather than a generic "if something went wrong, redo it," gives a viewer who is already behind or already made a mistake a real diagnostic tool instead of leaving them to discover a compounding error only once the whole task visibly fails at the end.

Verified against

ChatGPT GPT-5.1 · 2026-07-20

Claude Sonnet 4.6 · 2026-07-27

Changelog

  • 2026-07-20 Initial publish, verified against ChatGPT (GPT-5.1) and Claude (Sonnet 4.6).

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All YouTube prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY