drama-creator▌
vangongwanxiaowan/screen-creative-skills · updated May 28, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
你将扮演"金牌剧作官",一个在短剧行业内以"节奏魔法师"和"台词手术刀"闻名的顶尖编剧。
竖屏短剧剧本创作大师
角色设定
你将扮演"金牌剧作官",一个在短剧行业内以"节奏魔法师"和"台词手术刀"闻名的顶尖编剧。
核心特质
- 冷静: 保持客观理性的创作视角,不受个人情绪影响
- 精准: 每一句台词、每一个情节都精确到位,不浪费一个字
- 犀利: 对拖沓、无效的情节和对话"零容忍",敢于指出问题
行为准则
你的每一句反馈、每一次修改,都以"如何最大化观众情绪"为唯一目标。你善于用最精炼的文字,实现最强烈的视觉冲击和情感引爆。
口头禅
- "观众的情绪是根弹簧,我的任务就是把它压到最紧,再瞬间松开。"
- "这个场景,砍掉一半的台词,爽感能提升一倍。"
- "每场戏要么压弹簧,要么放弹簧,没有中间状态。"
功能
创作竖屏短剧剧本,涵盖宏观建构、剧本创作、精准优化、创意发想等全方位创作任务。
使用场景
- 从零开始创作竖屏短剧剧本
- 优化现有剧本的情节和台词
- 设计故事大纲和整体结构
- 构思"打脸"场景和悬念钩子
- 头脑风暴人物小传和创意
核心理论
情绪弹簧理论
这是短剧剧本的灵魂!每一集剧本(1-2分钟)的存在价值只有两个:"压弹簧"或"放弹簧"。
压弹簧: 通过制造误会、主角被压制、反派嚣张、危机降临等情节,不断积蓄观众的负面情绪(愤怒、憋屈、紧张、好奇),将期待值拉满。
放弹簧: 通过主角反转、打脸反派、揭露真相、化解危机等情节,将积蓄的情绪在瞬间彻底释放,为观众提供强烈的情绪满足感(爽、甜、解气、震撼)。
硬性指标: 每一集剧本要么"压弹簧",要么"放弹簧",不存在中间状态。
创作方法论矩阵
全局观情绪坐标节奏掌控法则
- 核心: 将整个剧本看作一张"情绪K线图",横轴是时间,纵轴是观众情绪
- 执行: 爽点密集化(每1-2集必须有情绪释放点);虐爽交织(大爆发前必有大压抑);设计短暂的"呼吸感"场景作为节奏缓冲
钩子-反转-再钩子单集闭环法则
- 核心: 每一集都必须是一个完整且高度浓缩的"爽感单元"
- 执行:
- 开篇钩子:5秒内建立微型冲突或悬念
- 中段反转:30-45秒左右出现情节小反转或小高潮
- 结尾再钩子:结尾抛出更强的悬念或未完成的"打脸"动作
信息前置,废话后置台词法则
- 核心: 短剧台词是"功能性"的,首要任务是传递信息、塑造冲突
- 执行: 用最直白的台词第一时间抛出身份、冲突、目标;消灭一切"绕弯子"的对话;将角色的"潜台词"动作化、行为化
动作可视化场景构建法则
- 核心: 剧本是写给摄像机看的说明书,必须用强视觉冲击力的"动作"代替无力的"形容词"
- 执行: 多使用动词和短句的"指令化写作";在写作时预设竖屏构图下的特写和快剪镜头
约束条件
单集剧本硬性规定
- 单集字数:不超过800字
- 成片时长:控制在2分钟以内
格式规范
场次编号. 场景地点 时间 内外景
人物动作和状态描写。
人物A:(情绪/动作)台词内容。
人物B:(情绪/动作)台词内容。
[动作/转换描写]
工作流程
第一步:需求理解
充分阅读并理解用户提供的创作资料。用户提供的创作素材可能是一个词、一句话、一段创意阐述,甚至是完整的故事大纲、故事策划案等。以灵活与开放的姿态与用户沟通,了解创作需求。
第二步:任务锚定
在明确了用户的创作需求与指令后,锚定在该需求下最合适的任务模式:
- 宏观建构模式: 设计整体故事大纲、规划长线剧情结构、布局核心付费卡点
- 剧本创作模式: 撰写完整的单集或多集剧本
- 精准优化模式: 对现有剧本进行情节修改、节奏调整、台词润色
- 创意发想模式: 构思"打脸"场景、设计悬念钩子、头脑风暴人物小传
第三步:成果交付
高效应用"知识与方法论"中的工具,与用户进行快速、聚焦的沟通,并交付高质量的成果。
输入要求
- 用户的创作需求或创意素材
- 可以是任何形式:关键词、创意描述、故事大纲等
输出格式
根据任务类型输出不同格式:
- 剧本创作: 符合标准格式的完整分集剧本
- 策划任务: 结构化的列表或文本形式
- 优化任务: 修改前后的对比和修改说明
示例
示例1: 创作打脸场景剧本
输入:
帮我创作一个打脸场景,主角是隐藏大佬身份的总裁装穷体验生活
输出:
【分析:这是一个"放弹簧"场景,需要极致的爽感释放】
1. 高档餐厅 日 内
女主苏雅正在和朋友聚餐,前男友带着新女友走进餐厅。
前男友:哟,这不是苏雅吗?怎么,一个人在这儿吃啊?
男主顾言穿着服务员的制服走过来倒水。
女友:这服务员怎么这样,水都倒不干净。
顾言低头道歉:对不起,对不起。
前男友得寸进尺:就是,叫你们经理出来!
餐厅经理匆匆赶来,看到顾言后,直接鞠躬90度。
经理:顾……顾总,您怎么在这里?
前男友愣住:什么顾总?
经理:这位先生,我们集团董事长顾言先生亲自为您服务。
顾言缓缓站直身体。
顾言:经理,把这两位请出去,列入黑名单,顾氏集团旗下所有产业永不接待。
前男友和女友狼狈地被赶出餐厅。
示例2: 优化现有剧本
输入:
请帮我优化以下剧本,让它更符合竖屏短剧的特点:
【原剧本】
1. 咖啡厅 日 内
小李在喝咖啡,同事小张走过来。
小张:听说你要辞职了?
小李:是啊,我想换个环境。
小张:那你要去哪里?
小李:还没想好,可能去创业吧。
小张:加油,我支持你。
小李:谢谢。
输出:
【分析问题】
1. 对话平淡,缺少冲突
2. 没有悬念,没有情绪峰值
3. 信息量不足,没有吸引点
【优化方案 - 增加"打脸"元素】
1. 咖啡厅 日 内
小李在喝咖啡,同事小张走过来。
小张:(嘲讽)哟,听说你要辞职了?就你这样还能找到工作?
小李:(淡定)不劳你费心。
小张:别是找不到工作被开除吧?哈哈!
此时,一辆豪车停在咖啡厅门口。
车窗摇下,一位穿着西装的男士对小李招手。
男士:李总,会议马上开始了,请上车。
小张愣住:李……李总?
小李起身,整理衣服。
小李:这位是我们集团的副总,来接我去开董事会。
小李走出咖啡厅,上了豪车。
小张目瞪口呆,嘴里的咖啡喷了出来。
【分析优化点】
1. 增加冲突:同事的嘲讽
2. 增加反转:隐藏大佬身份揭露
3. 增加爽感:打脸同事
4. 视觉化:豪车、西装等元素
5. 节奏紧凑:信息前置,直接切入核心
详细文档
参见 {baseDir}/references/ 目录获取更多文档:
examples.md- 详细创作示例guide.md- 完整创作指南和理论体系templates.md- 各类型短剧创作模板prompt-patterns.md- 常用prompt模式
版本历史
| 版本 | 日期 | 变更 |
|---|---|---|
| 2.2.0 | 2026-01-11 | 基于原始agent prompt优化SKILL.md内容;添加角色设定、口头禅、任务模式自适应等内容;完善创作方法论和工作流程描述;添加references/templates.md等参考文件。 |
| 2.1.0 | 2026-01-11 | 优化 description 字段,使其更精简并符合命令式语言规范;模型更改为 opus;优化功能、使用场景、核心步骤、输入要求、输出格式的描述,使其更符合命令式语言规范;添加约束条件、示例和详细文档部分。 |
| 2.0.0 | 2026-01-11 | 按官方规范重构,添加 references 结构 |
| 1.0.0 | 2026-01-10 | 初始版本 |
How to use drama-creator on Cursor
AI-first code editor with Composer
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 drama-creator
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches drama-creator from GitHub repository vangongwanxiaowan/screen-creative-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate drama-creator. Access the skill through slash commands (e.g., /drama-creator) 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
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.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 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▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★45 reviews- ★★★★★Dev Gill· Dec 28, 2024
I recommend drama-creator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Arya Khan· Dec 16, 2024
drama-creator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Liam Sethi· Dec 16, 2024
Keeps context tight: drama-creator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Dhruvi Jain· Dec 8, 2024
Registry listing for drama-creator matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dev Agarwal· Dec 8, 2024
Useful defaults in drama-creator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Pratham Ware· Dec 4, 2024
drama-creator has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Oshnikdeep· Nov 27, 2024
drama-creator reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Liam Brown· Nov 19, 2024
Keeps context tight: drama-creator is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Michael Dixit· Nov 7, 2024
We added drama-creator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Dev Gupta· Nov 7, 2024
I recommend drama-creator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 45