screen-recording-tutorial

name	screen-recording-tutorial
category	media
description	Make a screen-recorded tutorial on something they know. OBS set up, beats scripted, recorded, edited, published. Use when they say "I want to make a tutorial", "record my screen", or just solved something worth showing.

screen-recording-tutorial

Make a screen-recording tutorial with someone, about something they genuinely know how to do — a tool they use, a trick they figured out, the project they just built. Teaching on camera is proof of skill that goes straight on a resume. The session ends with the tutorial published or exported.

Pick the right topic

• It must be something they have done themselves. Re-run every step against the current tool before recording and use official documentation for anything uncertain. A tutorial may include research; it may not present guesses as instructions.
• Small beats comprehensive: "how I set up X in 5 minutes" beats "complete guide to X". One task, done start to finish.
• Best source: whatever they made or solved this month. A tutorial on their own project doubles as a demo of it.

OBS setup

OBS Studio is free on every platform. Ten minutes of setup:

• Scene with a Display Capture (or Window Capture for just the app — fewer notification accidents). 1920x1080 canvas, 30 fps.
• Mic input added and tested: speak at recording volume, keep the meter peaking in the yellow, never red. The record-clean-audio skill applies — quiet room, mic close.
• Do-not-disturb on the OS, close every app not in the tutorial, hide bookmarks and personal tabs, bump the app's font/zoom so text is readable at 1080p on a phone.
• Use a clean demo account and test data. Remove API keys, tokens, real email, private messages, file paths with personal names, and notifications from the screen before the test recording.
• Record a 20-second test, watch it back: audio present, cursor visible, text legible. Never skip the test.

Script beats, then record

Not a word-for-word script — a beat sheet:

1. Cold open on the result: show the finished thing working, one sentence on what this is and who it is for. This is the hook.
2. The steps, in the order a beginner needs them, including the one step everyone forgets (they know which one — ask them).
3. The mistake: the error or dead end they hit when learning it, and how to recognize it. This is the part only they can teach.
4. Close: recap in one line, where the code/files live if shared.

Record in one pass per beat. Mistakes mid-beat: pause two seconds, redo the beat — long pauses are easy to find and cut. Talking while doing is the skill; if narrating live is too much, record the screen actions first, then voice-over the footage while watching it play back.

Edit and publish

• Cut the pauses and redos; tighten anything where the screen is loading or nothing moves (speed those stretches up 4–8x rather than cutting, so continuity survives).
• Zoom/punch-in on small UI moments if the editor supports it.
• Captions pass per the captions-and-subtitles skill — tutorials get watched muted at desks constantly.
• Export 1080p MP4 and publish per publish-to-youtube: a title that names the task and the tool, a description with links to anything shown, timestamps per beat.

Done

• Tutorial live (or exported, if they publish later), watched end to end by both of you
• A stranger could follow it and land the same result
• Every shown step was re-run successfully and no private data or secret is visible
• The link recorded somewhere useful — resume, README, portfolio