Token导航 LogoToken导航

Agent Skill · 待分类

vsl-storyboard-writer(vsl 故事板编写器)

vsl-storyboard-writer 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

vsl-storyboard-writer 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 1,140。

总安装 4,872周安装 203GitHub Stars 18下载 1,624核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:vsl-storyboard-writer(vsl 故事板编写器)
来源仓库:https://github.com/ncklrs/startup-os-skills
仓库路径:skills/vsl-storyboard-writer
安装命令:
npx skills add https://github.com/ncklrs/startup-os-skills --skill vsl-storyboard-writer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/ncklrs/startup-os-skills --skill vsl-storyboard-writer

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

用于处理 GitHub 仓库、Issue、Pull Request 等协作信息。适合在故事板开发中跟踪项目状态与代码变更。vsl-storyboard-writer 属于待分类类 Skill,可作为该场景下的辅助能力补充。支持对 Issue 和 PR 进行归类与上下文提取。安装前应确认是否会触发网络请求或文件读写操作。

建议参考原始 README 了解具体集成方式与安全策略。

来源仓库内路径:skills/vsl-storyboard-writer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/ncklrs/startup-os-skills --skill vsl-storyboar…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

vsl-storyboard-writer 怎么安装?

在终端执行 npx skills add https://github.com/ncklrs/startup-os-skills --skill vsl-storyboard-writer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

vsl-storyboard-writer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

vsl-storyboard-writer 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

vsl-storyboard-writer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

vsl-storyboard-writer 用的人多吗?

公开数据是累计安装 4,872 次,近一周安装 203 次,下载 1,624 次,GitHub 18 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

vsl-storyboard-writer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
vsl-storyboard-writer

vsl 故事板编写器 · 本页

4,87218只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

VSL Storyboard Writer

Expert video sales letter and product marketing script writer specializing in high-converting video content that drives action. This skill bridges copywriting and video production, creating storyboard scripts ready for motion design implementation.

Philosophy

Great video sales scripts combine three elements:

  1. Sales psychology — Understanding what drives decisions at each stage
  2. Visual storytelling — Every scene advances both narrative and conversion
  3. Production readiness — Scripts that motion designers can implement immediately

How This Skill Works

When invoked, this skill guides you through creating storyboard scripts that include:

  • Hook-focused openings — Proven patterns to grab attention in 3-5 seconds
  • Narrative flow — Story structures that build desire and urgency
  • Scene-by-scene scripts — Visual descriptions, copy, timing, and rationale
  • Conversion optimization — Strategic placement of social proof, objection handling, CTAs
  • Motion design handoff — Format compatible with /motion-designer skill

The output is a complete storyboard script that feeds directly into the motion designer workflow for Remotion implementation.

Core Frameworks

VSL Formula Hierarchy

Choose framework based on video length and objective:

FormulaBest ForDurationStructure
Hook-CTASocial media ads15-30sProblem → Solution → CTA
PASCold traffic30-90sProblem → Agitation → Solution
AIDAProduct demos60-120sAttention → Interest → Desire → Action
VSL ClassicSales pages3-10minStory → Problem → Solution → Proof → Offer → CTA
The ExplainerEducation-first60-180sContext → How it works → Benefits → CTA

The 5-Second Hook Formula

First 5 seconds determine 80% of watch-through rate.

Hook Types:

  1. Question Hook — "What if [desired outcome] was actually easy?"
  2. Problem Hook — "Tired of [pain point]?"
  3. Curiosity Hook — "This [simple thing] changed everything"
  4. Pattern Interrupt — Unexpected visual or statement
  5. Social Proof Hook — "10,000 teams already [outcome]"
  6. Demonstration Hook — Show impressive result immediately

Video Length Guidelines

DurationTypeGoalKey Metrics
6-15sMicro-contentAwareness, viralityShares, engagement
15-30sSocial adsTraffic, interestCTR, view-through
30-60sProduct teasersDemo requestsClick rate
60-90sExplainersUnderstandingWatch time
90-180sFull demosTrial signupsConversion rate
3-10minVSL sales videosPurchase decisionsSales

The AIDA Arc for VSL

Attention (0-15%):

  • Hook with problem or question
  • Pattern interrupt
  • Relatable scenario

Interest (15-40%):

  • Agitate the problem
  • Show why current solutions fail
  • Introduce unique mechanism

Desire (40-80%):

  • Demonstrate solution in action
  • Social proof and testimonials
  • Paint the transformation
  • Handle objections

Action (80-100%):

  • Clear, specific offer
  • Urgency or scarcity
  • Risk reversal
  • Multiple CTAs

The PAS Framework

Problem (0-25%):

  • Identify specific, relatable pain point
  • Use "you" language
  • Visual: Show the struggle

Agitate (25-50%):

  • Why this problem is getting worse
  • Cost of inaction
  • Failed alternatives
  • Visual: Amplify the frustration

Solution (50-100%):

  • Introduce your product/service
  • Show it working
  • Proof it works
  • Easy next step
  • Visual: Transformation moment

Storyboard Script Format

When creating a storyboard, use this structure:

1. Script Header

# [Video Title]

**Type**: [VSL / Explainer / Product Demo / Social Ad]
**Duration**: [Total seconds]
**Objective**: [Primary conversion goal]
**Target Audience**: [Specific persona]
**Framework**: [AIDA / PAS / Hook-CTA / etc.]

## Key Message
[Single sentence: What should viewers remember?]

## Desired Action
[Specific CTA: What should viewers do?]

2. Script Overview

## Story Arc

**Hook (0-Xs)**: [How we grab attention]
**Build (Xs-Ys)**: [How we build interest/desire]
**Peak (Ys-Zs)**: [Climax / main value proposition]
**Close (Zs-End)**: [CTA and resolution]

## Emotional Journey
Start: [Frustrated / Curious / Overwhelmed]
→ Middle: [Hopeful / Intrigued]
→ End: [Confident / Excited to act]

3. Scene-by-Scene Storyboard

For each scene:

## Scene N: [Scene Name] (Xs - Ys, Duration: Zs)

**Narrative Purpose**: [Why this scene exists in the story]

**On-Screen Copy**:
"[Exact text that appears on screen]"
[Additional text elements]

**Voiceover Script** (Optional):
"[Exact words spoken, if using VO]"

**Visual Description**:
[What viewers see - specific enough for motion designer]
- Background elements
- Main focal point
- Supporting visuals
- Text treatment

**Viewer Psychology**:
[What the viewer should think/feel at this moment]
- Emotional state we're creating
- Objection we're handling (if applicable)
- Desire we're building

**Sales Elements**:
[Any conversion tactics used]
- Social proof placement
- Scarcity/urgency indicator
- Risk reversal
- Benefit emphasis
- Objection handling

**Transition to Next**:
[How this scene flows to the next - why it makes sense]

**Motion Designer Notes**:
[Specific animation suggestions or requirements]
- Timing emphasis (fast/slow)
- Style notes (bold/subtle)
- Key moments to emphasize

4. Production Requirements

## Assets Needed
- [ ] Logo files
- [ ] Product screenshots/mockups
- [ ] Customer photos (if using testimonials)
- [ ] Data visualization elements
- [ ] Icons

## Copy Elements
- Headlines: [List all]
- Subheads: [List all]
- CTAs: [List all instances]
- Social proof quotes: [List all]

## Brand Guidelines
- Voice: [Professional / Casual / Technical / Friendly]
- Tone: [Urgent / Calm / Exciting / Authoritative]
- Restrictions: [Any copy or visual rules]

VSL Storyboard Template

Here's a complete template for quick reference:

# [Video Title]

**Type**: Product Demo VSL
**Duration**: 90 seconds
**Objective**: Trial signups
**Framework**: AIDA
**Target**: [Persona]

## Story Arc
Hook (0-5s): Problem question
Build (5-30s): Agitate pain, show solution
Peak (30-70s): Demo + social proof
Close (70-90s): CTA + urgency

---

## Scene 1: Hook (0-5s)

**On-Screen Copy**:
"Spending hours on [task]?"

**Visual**: [Description]
**Psychology**: Immediate identification with pain
**Sales Element**: Problem recognition
**Transition**: Visual chaos → order

---

## Scene 2: Agitation (5-15s)

**On-Screen Copy**:
"While your competitors move faster?"

**Visual**: [Description]
**Psychology**: FOMO, urgency of problem
**Sales Element**: Cost of inaction
**Transition**: Dark → light

---

[Continue for all scenes...]

Integration with Motion Designer

This skill produces storyboard scripts that the /motion-designer skill uses to create technical video specifications:

Storyboard Script (this skill) → Video Spec (motion-designer) → Remotion Implementation (dev)

When creating storyboards:

  1. Focus on copy, messaging, and conversion strategy
  2. Provide visual direction but not technical specs
  3. Include timing guidance but not frame-by-frame details
  4. Emphasize WHY each scene exists (narrative + conversion)
  5. Let motion designer handle HOW to execute visually

Common Video Types

Short-Form Social (15-30s)

Formula: Hook → Value → CTA

Scene 1 (0-3s): Bold question or problem
Scene 2 (3-12s): Show solution in action (demo)
Scene 3 (12-20s): Single benefit + social proof number
Scene 4 (20-30s): Simple CTA

Product Explainer (60-90s)

Formula: Context → Demo → Benefits → CTA

Scene 1 (0-5s): Relatable problem hook
Scene 2 (5-15s): Why existing solutions fail
Scene 3 (15-30s): Introduce your solution
Scene 4 (30-50s): Show it working (3 key features)
Scene 5 (50-70s): Transformation / benefits
Scene 6 (70-80s): Social proof
Scene 7 (80-90s): Clear CTA

Full VSL (3-5min)

Formula: Story → Problem → Solution → Proof → Offer → Close

Act 1 - Setup (0-45s):
  - Personal story or customer story
  - Establish credibility
  - Introduce problem

Act 2 - Problem (45s-90s):
  - Deep dive into pain points
  - Why current solutions don't work
  - Cost of status quo

Act 3 - Solution (90s-180s):
  - Introduce product/service
  - Unique mechanism
  - How it works (demo)
  - Key benefits

Act 4 - Proof (180s-240s):
  - Case studies
  - Testimonials
  - Results/data
  - Objection handling

Act 5 - Offer (240s-270s):
  - What you get
  - Pricing
  - Bonuses
  - Guarantee

Act 6 - Close (270s-300s):
  - Urgency/scarcity
  - Final CTA
  - Reminder of transformation

Conversion Optimization Principles

Social Proof Placement

  • Early social proof (15-25% mark): Build credibility before big claims
  • Feature proof (40-60% mark): Testimonials after each key benefit
  • Final proof (80-90% mark): Results-focused before CTA

Objection Handling Sequence

Common objections to address in order:

  1. Does it work? → Demo + proof
  2. Will it work for me? → Use cases / customer stories
  3. Is it too complicated? → Show simplicity
  4. Is it worth the money? → ROI / value equation
  5. What if it doesn't work? → Guarantee / risk reversal

CTA Best Practices

  • Frequency: Minimum 2 CTAs (mid-point teaser + final)
  • Clarity: Specific action ("Start free trial" not "Learn more")
  • Friction: Remove ("No credit card" if true)
  • Urgency: Time or quantity limits (if genuine)

Anti-Patterns

Script-Level

  • Feature dumping — List features without benefits or story
  • No hook — Slow build that loses viewers immediately
  • Unclear CTA — Vague next step or multiple competing CTAs
  • All tell, no show — Talking about product instead of showing it
  • Dishonest urgency — Fake countdown timers, false scarcity

Scene-Level

  • Wall of text — Too much copy on screen at once
  • Orphaned scenes — Scene doesn't advance narrative or conversion
  • No breathing room — No time for messages to land
  • Inconsistent tone — Voice shifts between scenes

Production

  • Not production-ready — Vague visuals that motion designer must guess
  • Missing timing — No scene durations or pacing guidance
  • No assets list — Unclear what's needed to produce

Quality Checklist

Before finalizing a storyboard script:

Hook & Structure:

  • Attention grabbed within 3-5 seconds
  • Clear story arc (hook → build → peak → close)
  • Framework appropriate for duration and goal
  • Emotional journey intentional and clear

Copy & Messaging:

  • Single, clear key message
  • Benefits emphasized over features
  • "You" language (viewer-focused)
  • On-brand voice and tone
  • No jargon or unexplained terms

Conversion Elements:

  • Social proof strategically placed
  • Main objections addressed
  • Clear, specific CTA
  • Urgency or scarcity (if appropriate)
  • Risk reversal included

Production Readiness:

  • All scene timings specified
  • Visual descriptions clear and specific
  • Required assets listed
  • Motion designer notes included
  • Narrative purpose explained for each scene

Integration:

  • Format compatible with motion-designer skill
  • Ready for handoff without clarification needed
  • Technical constraints considered (duration, format)

When to Consult Rules

For detailed guidance on specific aspects:

Expert Tips

Script Writing

  • Start with the CTA, work backwards (what journey gets them there?)
  • Write for the ear if using voiceover (conversational, not formal)
  • One message per scene (don't try to say everything everywhere)
  • Test your hook independently (does it work as a standalone ad?)

Conversion Psychology

  • Lead with transformation, not features
  • Use specific numbers ("10,000 customers" not "thousands")
  • Name the pain before naming the solution
  • Create urgency through value, not fake scarcity

Production Planning

  • Plan for silent viewing (60%+ watch without sound)
  • Consider aspect ratios early (16:9, 9:16, 1:1)
  • Budget 30% longer than you think for final duration
  • Leave flexibility for motion designer creativity

Collaboration

  • Provide examples of visual style you envision
  • Reference other videos when helpful ("like X but for Y")
  • Be clear about non-negotiables vs nice-to-haves
  • Trust motion designer for technical execution

平台分布

Codex

35.03%
按下载量换算569

Claude

30.14%
按下载量换算489

Cursor

19.88%
按下载量换算323

Gemini CLI

9.33%
按下载量换算152

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills