technical-video-script

Writes shooting-ready two-column beat scripts for technical videos and screencasts.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill technical-video-script-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-video-script
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/technical-video-script
Command: npx skills add https://github.com/samber/developer-relations-skills --skill technical-video-script-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical videos fail at the script stage: openings that bury the payoff past the 30-second retention window, narration full of deictic phrases like "click here" that break captions and accessibility, runtimes that double during recording because dead time was never budgeted, and no cut list when the edit runs long. This Skill produces a script a stranger could record from, or diagnoses why an existing script or published video underperforms. ## Core Features & Use Cases - Beat-sheet generation: Produces a two-column visual/narration beat table with per-beat starting states, duration estimates including dead time, core/cuttable markings, chapter titles, a cut plan, and a recording brief. - Shape selection: Picks among seven video shapes (error/fix, changelog clip, short-form, walkthrough, concept explainer, build-along, deep dive) ranked by production effort against the interview's constraints, deleting shapes the team cannot support. - Script review and diagnosis: Grades an existing script beat by beat against a three-cause model (logic break, density drop, unspeakable line) with high/medium/low risk levels, showing original lines beside proposed replacements. - Use Case: Turn a 2,100-word engineering blog post into a 3-minute launch video: the Skill interviews for promise, viewer and constraints, transposes the post into claims rather than headings, and returns a beat sheet with chapters, cut plan and recording brief. ## Quick Start Ask the assistant to turn your blog post, changelog entry, or working demo into a shooting-ready video script with a beat table, chapter list, and recording brief.

Frequently Asked Questions about technical-video-script

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a blog post into a technical video script?

Transpose the post into the claims it proves rather than copying its section headings, keep only the claims the video's promise needs, then write one beat per claim in a two-column visual/narration table. Background sections are usually the first thing cut.

How long should a technical tutorial video be?

Published research on 6.9 million viewing sessions found median engagement is at most six minutes regardless of total length, so segment videos into chapters under roughly six minutes. Procedural tutorials are typically watched two to three minutes at a time regardless of length.

Why do viewers drop off in the first 30 seconds of my demo video?

The opening usually fails because the payoff sits outside the 30-second window the platform's retention report measures. The first beat must name the viewer's problem, show the result already running, state prerequisites, and state the runtime, with ceremony capped near five seconds.

How do I make screencast narration accessible without a separate audio description track?

Use integrated description: write the visual information into the main narration by naming identifiers, values and UI destinations instead of saying "click here" or "as you can see". Then run an audio-only pass to verify the narration alone still teaches the content.

Should I type code live on camera in a screencast?

Type only the lines the video is about; pre-supply, paste or snippet-expand imports, boilerplate and config. Narrate before revealing code rather than during, hold the frame silently after results appear, and keep terminal text at 24pt and editor text at 20pt or larger.

When should I not use this video scripting skill?

It does not cover live stage demos, conference talks, podcast appearances, written documentation, video editing or rendering, or deciding which videos to produce this quarter. Those tasks route to other skills in the developer-relations collection.