narration-script
Write the spoken voiceover for a tutorial or demo - the actual words, phrased for the ear and synced one-instruction-per-action to what is on screen, with a pacing budget and a confident, jargon-checked tone. Use when someone says "write the voiceover", "script the narration", "what should I say over this", "VO script for my tutorial", "narrate this demo", "the script feels robotic", or "the narration is too wordy". Do NOT use to mix, time, duck, source, or beat-match the audio - VO leveling, SFX, music - that is sound-and-music-sync; do NOT use to decide which scenes exist or their order - that is video-storyboard; do NOT use to direct the on-screen actions themselves (cursor, zoom, callouts) - that is product-demo-director; do NOT use to turn spoken lines into animated on-screen text - that is kinetic-typography.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- narration-script
- metadata
- { "title": "Narration Script" }
- description
- Write the spoken voiceover for a tutorial or demo - the actual words, phrased for the ear and synced one-instruction-per-action to what is on screen, with a pacing budget and a confident, jargon-checked tone. Use when someone says "write the voiceover", "script the narration", "what should I say over this", "VO script for my tutorial", "narrate this demo", "the script feels robotic", or "the narration is too wordy". Do NOT use to mix, time, duck, source, or beat-match the audio - VO leveling, SFX, music - that is sound-and-music-sync; do NOT use to decide which scenes exist or their order - that is video-storyboard; do NOT use to direct the on-screen actions themselves (cursor, zoom, callouts) - that is product-demo-director; do NOT use to turn spoken lines into animated on-screen text - that is kinetic-typography.
03 SKILL.md 正文
Narration Script
A tutorial lives or dies on its narration. The viewer is trying to do the thing while listening, so every word competes with their attention on the screen. Write less, say it plainer, and pin each line to a visible action.
Write for the ear, not the page
Spoken language is not written language. Read every line aloud before keeping it.
- Short sentences. One idea each. If you run out of breath, it is too long.
- Active voice, present tense, second person: "Click Save" - not "The Save button would then be clicked by the user."
- Cut every "basically", "simply", and "just." "Just click Settings" quietly tells a stuck viewer they are stupid. Drop it.
- Contractions are good ("you'll", "it's"); they sound human.
Sync narration to action
The cardinal rule: one instruction per on-screen action, and the words land with the action, never describing what already happened.
- State the action a beat before or exactly as it happens on screen, so the viewer's hand and the cursor move together.
- Never narrate a click that has already finished - "and now we've saved it" after the save animation is dead air.
- When the screen does something complex, stop talking and let it breathe. Silence over a clear visual beats narration fighting it.
Pace it
- Target ~140-160 words per minute for instruction. Faster loses people who are following along.
- Budget the script against the storyboard's per-scene durations. If a beat is 8 seconds, that is ~20 words, not 50.
- Build in deliberate pauses at transitions and at any moment the viewer needs to look rather than listen.
Structure each step
A reliable three-part shape per step keeps viewers oriented:
- Goal - what we're about to do and why ("To share this, we'll create a public link.").
- Action - the single concrete instruction ("Open the Share menu and choose Anyone with the link.").
- Confirmation - what success looks like ("You'll see the link turn green when it's ready.").
Signpost between steps with light transitions - "Next", "Now that the link exists, let's…" - so the spine of the tutorial is always audible.
Tone
Confident and warm, like a competent colleague sitting beside them. Never condescending, never hype. Define a term the first time it appears, then use it consistently. Match on-screen UI labels exactly - if the button says "New project", say "New project", not "create a project."
Output format
Deliver a two-column script the editor and VO talent can both follow:
| On-screen action | Spoken line |
|---|---|
| Cursor opens Share menu | "Open the Share menu in the top right." |
| Link toggles to public | "Switch it to Anyone with the link." |
Mark [pause] where the visual should carry the moment, and bold the words to stress. Note approximate timing per line if the storyboard durations are known.
Don't
- Don't write music, SFX, or mix cues here - pacing the audio, ducking, and beat-matching is sound-and-music-sync.
- Don't plan the scene order or shot list - that is video-storyboard, which this script should follow.
- Don't describe filler the viewer can already see ("here is the screen, as you can see there are some buttons").
- Don't let a line outrun its scene's duration budget; trim words, not pauses.
04 同仓库更多 Skills
有氧运动计划
zone-2-cardio-plan
当有人要求制定稳态有氧训练计划、进行有氧基础训练或达到第二区间、安排轻松或耐力型的每周有氧训练、按心率区间训练，或提高静息心率、最大摄氧量或耐力时，可以使用此方案。该方案构建了一个包含训练计划结构、训练方式选择和进度安排的心率区间有氧训练模块。本方案仅提供一般健身指导，不构成医疗建议。请勿用于设计力量或举重训练计划（请使用力量训练计划）、高强度间歇训练 (HIIT) 或循环训练（请使用体能训练和 HIIT 计划），或灵活性/柔韧性训练（请使用灵活性训练计划）。
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.