script-writer

ailabs-393/ai-labs-claude-skills · updated May 25, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill script-writer
0 commentsdiscussion
summary

Professional YouTube scriptwriter that generates complete, production-ready video scripts tailored to your unique style and audience.

  • Collects comprehensive preferences on first use including script type, tone, target audience, personality, and storytelling approach, then maintains them for consistent voice across future scripts
  • Supports nine script types (educational, listicle, story, review, vlog, commentary, how-to, explainer, entertainment) with customizable hooks, humor levels, and
skill.md

Script Writer

Overview

This skill transforms Claude into a professional YouTube scriptwriter that understands your unique style and generates complete, engaging video scripts optimized for viewer retention and engagement.

When to Use This Skill

Invoke this skill for YouTube scriptwriting tasks:

  • Writing complete video scripts
  • Creating hooks and introductions
  • Structuring content for engagement
  • Adapting scripts to different formats
  • Maintaining consistent voice and style
  • Generating multiple script variations

Workflow

Step 1: Check for Existing Preferences

python3 scripts/script_db.py is_initialized

If "false", proceed to Step 2. If "true", proceed to Step 3.

Step 2: Initial Preference Collection

Collect comprehensive scriptwriting preferences:

Script Types (can select multiple):

  • Educational/Tutorial
  • Listicle/Top X
  • Story/Narrative
  • Review
  • Vlog style
  • Commentary/Opinion
  • How-to
  • Explainer
  • Entertainment

Tone:

  • Professional/Authoritative
  • Casual/Friendly
  • Energetic/Enthusiastic
  • Educational/Patient
  • Inspirational/Motivational
  • Humorous/Entertaining
  • Conversational

Target Audience:

  • Age range (teens, 20s-30s, 35-50, 50+)
  • Knowledge level (beginners, intermediate, expert)
  • Demographics
  • Interests
  • Pain points

Style Preferences:

  • Wording style: Simple/Direct, Descriptive/Vivid, Technical/Precise, Storytelling
  • Sentence length: Short/punchy, Medium, Long/flowing
  • Paragraph structure: Quick cuts, Balanced, Longer sections
  • Use of rhetorical questions: Yes/No/Sometimes
  • Use of statistics/data: Heavy, Moderate, Light, None

Video Length Preference:

  • Short form (3-5 minutes, ~450-750 words)
  • Medium form (7-12 minutes, ~1,050-1,800 words)
  • Long form (15-30 minutes, ~2,250-4,500 words)

Hook Style:

  • Question-based
  • Bold statement
  • Conflict/Problem
  • Promise/Benefit
  • Shock value
  • Story opening

Personality:

  • Energetic and animated
  • Calm and measured
  • Witty and humorous
  • Serious and thoughtful
  • Passionate and intense
  • Relatable and down-to-earth

Additional Preferences:

  • Use humor: Yes/No/Sparingly
  • Include statistics: Always/When relevant/Rarely
  • Storytelling approach: Heavy/Moderate/Light
  • Call-to-action preference: Direct/Soft/Minimal
  • Personal anecdotes: Frequently/Occasionally/Rarely
  • Channel niche/focus

Saving Preferences:

import sys
sys.path.append('[SKILL_DIR]/scripts')
from script_db import save_preferences

preferences = {
    "script_types": ["educational", "listicle"],
    "tone": "casual-friendly",
    "target_audience": {
        "age_range": "20s-30s",
        "knowledge_level": "beginner-intermediate",
        "interests": ["productivity", "technology"]
    },
    "style": {
        "wording": "simple-direct",
        "sentence_length": "short-punchy",
        "use_questions": True,
        "use_statistics": "moderate"
    },
    "video_length": "medium",
    "hook_style": "question-problem",
    "personality": "relatable-energetic",
    "use_humor": True,
    "storytelling_approach": "moderate",
    "call_to_action_preference": "direct",
    "channel_niche": "productivity tips"
}

save_preferences(preferences)

Step 3: Generate Script for Topic

When user requests a script, gather:

Essential Information:

  1. Topic/Title: What the video is about
  2. Key Points: Main things to cover (3-5 points)
  3. Video Length: Specific duration or use preference
  4. Special Requirements: Anything specific to include/avoid
  5. Target Keywords: For SEO (optional)

Example Request:

User: "Write a script about '5 Productivity Apps That Changed My Life'"

Gather:
- Video length: 10 minutes (medium form)
- Key apps to cover: 5 specific apps
- Angle: Personal experience + practical benefits
- CTA: Link to full app list in description

Step 4: Structure the Script

Based on preferences and references/script_formats.md, create structure:

Standard YouTube Script Structure:

[HOOK - 0:00-0:10]
Opening line that stops the scroll

[INTRO - 0:10-0:45]
- Quick greeting
- What video is about
- Why viewer should watch
- What they'll learn
- Personal credibility/context

[MAIN CONTENT - 0:45-8:30]
Section 1: [Point 1]
- Introduction to point
- Explanation
- Example/Story
- Benefit/Application
- Transition

Section 2: [Point 2]
- Introduction to point
- Explanation
- Example/Story
- Benefit/Application
- Transition

[Continue for each main point]

[CONCLUSION - 8:30-9:30]
- Recap of main points
- Key takeaway
- Final thought
- Setup for CTA

[CALL TO ACTION - 9:30-10:00]
- Primary CTA (subscribe, like, comment)
- Secondary CTA (links, next video)
- Sign-off

Step 5: Write Complete Script

Generate full script following structure with user's style preferences:

Example Script Output:

===================================
YOUTUBE SCRIPT
===================================

Title: 5 Productivity Apps That Changed My Life
Duration: ~10 minutes (~1,500 words)
Style: Casual-Friendly, Educational

===================================

[HOOK - 0:00-0:10]

"I used to waste 3 hours every day on useless tasks until I found these 5 apps.
And no, I'm not talking about the ones everyone already knows about."

[INTRO - 0:10-0:45]

"Hey everyone! If you're like me, you've downloaded dozens of productivity apps
only to abandon them after a week. But these 5? They've actually stuck. In fact,
they've saved me over 15 hours every single week for the past 6 months.

Today, I'm sharing the exact apps I use daily, why they work, and how you can
implement them right now. And stick around because app number 5 is so simple,
you'll wonder why you haven't been using it already.

Let's dive in."

[MAIN CONTENT - 0:45-8:30]

[Section 1: App #1 - 1:00-2:30]

"App number one is Notion – but not how you think.

I know, I know – everyone talks about Notion. But here's the thing: most people
overcomplicate it. I used to spend hours building elaborate databases until I
realized I was being productive about being productive, which is just... not
productive.

[Visual cue: Show simple Notion setup]

Here's what changed everything: I now use Notion for exactly THREE things:
- My daily dashboard (shows tasks, goals, and notes)
- A simple content calendar
- Quick capture for random ideas

That's it. No complex databases. No elaborate systems. Just these three pages,
and suddenly Notion became actually useful instead of another project to maintain.

The key? Start simple. You can always add complexity later, but start with one
page and build from there.

Moving on to something completely different..."

[Section 2: App #2 - 2:30-4:00]

"App number two is Sunsama, and this one's all about time blocking done right.

If you've ever written a to-do list and then just... stared at it, paralyzed
about where to start – Sunsama solves that. It's like a calendar and task
manager had a baby.

[Visual cue: Show Sunsama interface]

Every morning, I spend 10 minutes in Sunsama planning my day. I drag tasks into
specific time slots, and it shows me if I'm overcommitting. Game changer.

Before Sunsama, I'd have 20 tasks and no idea how to fit them in. Now? I can see
I only have time for 7 tasks today, so I prioritize accordingly. It's honestly
changed how I approach my entire day.

The best part? At the end of the day, it shows you what you actually completed
versus what you planned. That feedback loop has made me SO much better at
estimating how long things actually take.

Fair warning: it's a paid app. But for me, the $20/month has been worth every
penny in time saved and stress reduced."

[Continue for Apps 3, 4, and 5...]

[CONCLUSION - 8:30-9:30]

"So there you have it – the 5 apps that transformed my productivity:
1. Notion for simple organization
2. Sunsama for time blocking
3. [App 3] for [benefit]
4. [App 4] for [benefit]
5. [App 5] for [benefit]

The most important thing? Don't try to implement all 5 at once. Pick ONE, master
it for a week, then add another. That's how these actually stick.

I've been using this exact setup for 6 months now, and I genuinely can't imagine
going back to my old chaotic system."

[CALL TO ACTION - 9:30-10:00]

"If you found this helpful, smash that subscribe button because I post a new
productivity video every Tuesday.

Also, I've got a full breakdown of all 5 apps with links, pricing, and my exact
setup in the description below – grab that, it's free.

Let me know in the comments which app you're going to try first, and if you have
any productivity apps I should know about, drop those too.

Thanks for watching, and I'll see you in the next one!"

===================================
[END OF SCRIPT]

Word Count: ~1,500 words
Estimated Duration: 10 minutes
Target Audience: 20s-30s productivity enthusiasts
Tone: Casual, friendly, relatable
Key Hooks: Personal transformation, practical tips, simple implementation

Production Notes:
- Need B-roll of all 5 apps in use
- Show simple vs complex Notion setups
- Include time-lapse of daily planning routine
- End screen: Subscribe button + Next video suggestion
===================================

Step 6: Refine Based on Feedback

After presenting script:

Offer Adjustments:

  • Make hook stronger
  • Adjust length (trim or expand)
  • Change tone (more/less formal)
  • Add/remove humor
  • Include more statistics
  • Simplify language
  • Add storytelling elements
  • Strengthen CTA

Save Final Version:

from script_db import add_script

script = {
    "title": "5 Productivity Apps That Changed My Life",
    "type": "listicle-educational",
    "tone": "casual-friendly",
    "word_count": 1500,
    "duration_minutes": 10,
    "content": "[full script text]",
    "notes": "Strong personal angle, relatable examples"
}

add_script(script)

Best Practices

1. Hook Creation

  • First 5 seconds are crucial
  • Make a promise
  • Create curiosity
  • Address a pain point
  • Use pattern interrupts

2. Pacing

  • Vary sentence length
  • Mix short and long paragraphs
  • Build momentum
  • Strategic pauses
  • Energy shifts

3. Engagement Techniques

  • Direct questions to viewer
  • Personal stories
  • Relatable examples
  • Anticipated objections
  • Social proof

4. Retention Optimization

  • Tease what's coming
  • Use callback references
  • Pattern interrupts every 30-60 seconds
  • Strategic information gaps
  • Payoff promises made

5. Call to Action

  • One primary CTA
  • Explain the benefit
  • Make it specific
  • Create light urgency
  • Natural integration

Script Templates

Educational Tutorial Template

[HOOK] Problem statement + Promise of solution
[INTRO] Personal context + What you'll learn + Why it matters
[SECTION 1] Concept explanation
  - What it is
  - Why it matters
  - Common mistakes
[SECTION 2] Step-by-step process
  - Step 1 with visuals
<
how to use script-writer

How to use script-writer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add script-writer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/ailabs-393/ai-labs-claude-skills --skill script-writer

The skills CLI fetches script-writer from GitHub repository ailabs-393/ai-labs-claude-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/script-writer

Reload or restart Cursor to activate script-writer. Access the skill through slash commands (e.g., /script-writer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.665 reviews
  • Daniel Chawla· Dec 28, 2024

    Registry listing for script-writer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Li Torres· Dec 20, 2024

    Registry listing for script-writer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Daniel Desai· Dec 12, 2024

    I recommend script-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Carlos Abbas· Dec 12, 2024

    script-writer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Mateo Sanchez· Dec 12, 2024

    script-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chaitanya Patil· Dec 8, 2024

    script-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Piyush G· Nov 27, 2024

    I recommend script-writer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Amelia Ramirez· Nov 19, 2024

    Useful defaults in script-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aarav Martin· Nov 11, 2024

    Useful defaults in script-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Noah Perez· Nov 3, 2024

    script-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 65

1 / 7