Agent skill · Code Review & Quality

youtube-script

Write a long-form video script for YouTube — an explainer, tutorial, video essay, review, or talking-head — built on the packaging→cold-open→value-stack→retention structure that holds watch-time past the drop-off cliffs. Use when asked to script a YouTube video, write a long-form or explainer/tutorial video script, outline a video essay, or turn a blog post/talk into a video. Produces title + thumbnail concepts, a timed cold open, a segmented body with retention devices and B-roll cues, integrated CTAs, an outro/end-screen, and a description with chapter timestamps. Distinct from [[short-form-

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill youtube-script --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/youtube-script/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# YouTube Script Skill Long-form video is won twice: first the **packaging** earns the click, then the **script** keeps the promise the packaging made. A YouTube video does not fail in the middle — it fails at predictable cliffs (the first 30 seconds, the ~2-minute mark, the midpoint). This skill writes a script engineered to survive those cliffs: a cold open that pays off fast, value delivered early and escalated, and an open loop pulling the viewer across every segment. ## Working from a brief Given a topic, a blog post, a talk transcript, or a rough outline, **write the full script anyway** — infer the single promise and the audience. Target the requested runtime (default ~8–12 min ≈ 1,200–1,800 spoken words; ~130–150 words/min). Never pad to hit a length; a tight 7 minutes beats a bloated 12. If the topic is genuinely short, say so and recommend [[short-form-script]] instead. ## Required Inputs Ask for (if not already provided, else infer and label the assumption): - **Topic / the idea** (or a source: blog post, transcript, docs) and the **one promise** the video delivers - **Audience** and their level (complete beginner → practitioner) - **Target runtime** (~5 / ~10 / ~20 min)

What's inside
Steps it walks through
  1. Working from a brief
  2. Required Inputs
  3. Output Format
  4. The promise
  5. Packaging (title + thumbnail)
  6. Cold open (0:00–0:30)
  7. Script (segmented)
  8. CTAs
  9. Outro & end-screen
  10. Description + chapters
  11. Quality Checks
  12. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the youtube-script skill do?

Write a long-form video script for YouTube — an explainer, tutorial, video essay, review, or talking-head — built on the packaging→cold-open→value-stack→retention structure that holds watch-time past the drop-off cliffs. Use when asked to script a YouTube video, write a long-form or explainer/tutorial video script, outline a video essay, or turn a blog post/talk into a video. Produces title + thumbnail concepts, a timed cold open, a segmented body with retention devices and B-roll cues, integrated CTAs, an outro/end-screen, and a description with chapter timestamps. Distinct from [[short-form-

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill youtube-script --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going