Story Multi-Perspective Review
zenstory-ai/oh-story-claudecode
Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.
Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida…
Install Sw Japanese Screenwriting
$ npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jtydhr88/screenwriting-skills sw-japanese-screenwriting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jtydhr88/screenwriting-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/screenwriting/skills/sw-japanese-screenwriting .claude/skills/sw-japanese-screenwriting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sw-japanese-screenwriting" agent skill from https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwriting into .claude/skills/sw-japanese-screenwriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sw-japanese-screenwriting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwritingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jtydhr88/screenwriting-skills sw-japanese-screenwriting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/screenwriting-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/screenwriting/skills/sw-japanese-screenwriting .agents/skills/sw-japanese-screenwriting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sw-japanese-screenwriting" agent skill from https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwriting into .agents/skills/sw-japanese-screenwriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sw-japanese-screenwriting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jtydhr88/screenwriting-skills sw-japanese-screenwriting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/screenwriting-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/screenwriting/skills/sw-japanese-screenwriting .cursor/skills/sw-japanese-screenwriting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sw-japanese-screenwriting" agent skill from https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwriting into .cursor/skills/sw-japanese-screenwriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sw-japanese-screenwriting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jtydhr88/screenwriting-skills.git --path plugins/screenwriting/skills/sw-japanese-screenwriting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jtydhr88/screenwriting-skills sw-japanese-screenwriting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/screenwriting-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/screenwriting/skills/sw-japanese-screenwriting .gemini/skills/sw-japanese-screenwriting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sw-japanese-screenwriting" agent skill from https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwriting into .gemini/skills/sw-japanese-screenwriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sw-japanese-screenwriting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jtydhr88/screenwriting-skills sw-japanese-screenwritingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jtydhr88/screenwriting-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/screenwriting/skills/sw-japanese-screenwriting .github/skills/sw-japanese-screenwriting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sw-japanese-screenwriting" agent skill from https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwriting into .github/skills/sw-japanese-screenwriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sw-japanese-screenwriting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jtydhr88/screenwriting-skills sw-japanese-screenwriting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtydhr88/screenwriting-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/screenwriting/skills/sw-japanese-screenwriting .opencode/skills/sw-japanese-screenwriting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sw-japanese-screenwriting" agent skill from https://github.com/jtydhr88/screenwriting-skills/tree/main/plugins/screenwriting/skills/sw-japanese-screenwriting into .opencode/skills/sw-japanese-screenwriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sw-japanese-screenwriting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sw-japanese-screenwriting- GitHub stars
- 1.6k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 207 words
- Files
- 2
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida…
- Works in 12 steps: 我是结构优先还是片段优先？选定后是否至少写完一部？ → 题目让人想问"是什么事"吗？梗概讲给三个人听反应如何？找到说"没意思"的人问"哪里… → 构想是两件相去甚远之物的加法吗？用了"而且"而非"进而"吗？ → …
- Writing an original Japanese-style script
- SKILL.md covers 一、两派方法：结构优先 vs 人物/片段优先, 二、结构与节奏, 三、素材与构想 and 四、人物, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sw Japanese Screenwriting is an agent skill from jtydhr88/screenwriting-skills. Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida Kenji (beautiful structure, time-axis tricks), Miki Satoshi (small-material notebook, theme emerges later), Sono Sion, Omiya Ellie (dialogue from inner monologue), Kakei Masaya ("if + moreover"), Fukuda Yuichi (character = actor + flaw, audience as tsukkomi), Yokohama Satoko, Takahashi Izumi ("pain"), Yukisada Isao…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `reference.md`).
It sits in Writing & Content, covering Creative writing and fiction. The repository describes itself as: Professional agent skills for screenwriting, television writing and dramaturgy. The licence is MIT.
When your agent uses it
- Writing an original Japanese-style script
- Working from small material and fragments
- Choosing between structure-first and character-first methods
- Building a Japanese 企画書
Example prompts
- “if + moreover”
- “write what you”
- “/sw-japanese-screenwriting”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- 我是结构优先还是片段优先？选定后是否至少写完一部？
- 题目让人想问"是什么事"吗？梗概讲给三个人听反应如何？找到说"没意思"的人问"哪里"了吗？
- 构想是两件相去甚远之物的加法吗？用了"而且"而非"进而"吗？
- 结尾定了吗（哪怕先有一个画面）？"承"够多够精彩吗？每场有跳跃感吗？后一句台词否定前一句了吗？
- 情况说明是否尽早结束？10 分钟内有事件吗？电视剧一卷 10 分钟 7 件事列了吗？
- 人物：履历/日记写了吗？从设定逆推了职业吗？演员的缺点想好了吗？"人品"而非"角色"（房间里那两本《哆啦 A 梦》）？名字定了吗？
- 素材：一天一条记了吗？取材/亲身经历用作突破口而非照搬？害羞的事暴露了吗？
- 主题：是让它自己浮现（浮现后删多余）还是先定？有没有说教？有指针性台词或镜头吗？
- 喜剧：逗捧分配了吗？捧哏交给观众了吗？"现实感"是不是只来自你看过的剧？
- 限制：这次的束缚是什么（预算、场地、演员档期、委托条件）？把它当武器了吗？
- 剧本留了议论与改变的余地吗？工作人员看了会兴奋吗？
- 主人公一定要有目标/成长吗？不成长的版本是否更真？日常的重复与偏离写出来了吗？
What it can do on your machine
Read from SKILL.md and the folder at commit 51115f1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sw Japanese Screenwriting loads about 2.1k tokens when it runs. Until then it costs about 254 tokens; SKILL.md has 207 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jtydhr88/screenwriting-skills at commit 51115f1, republished under its MIT licence (© jtydhr88). 207 words, ~2,107 tokens.
Download SKILL.mdSave it as
.claude/skills/sw-japanese-screenwriting/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- sw-japanese-screenwriting
- description
- Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida Kenji (beautiful structure, time-axis tricks), Miki Satoshi (small-material notebook, theme emerges later), Sono Sion, Omiya Ellie (dialogue from inner monologue), Kakei Masaya ("if + moreover"), Fukuda Yuichi (character = actor + flaw, audience as tsukkomi), Yokohama Satoko, Takahashi Izumi ("pain"), Yukisada Isao (situation-born originals); plus Arai Haruhiko (IP adaptation, "write what you're ashamed of"). Neighbours; sw-korean-french-screenwriting, ozu-screenplay-style. Use when writing an original Japanese-style script or TV drama, working from small material and fragments, choosing between structure-first and character-first methods, building a Japanese 企画書, designing comedy tsukkomi systems, or when Hollywood models feel wrong for a quiet, daily-life, non-goal-driven story.
日本编剧方法（Japanese Screenwriting Methods）
输出语言＝提问语言；术语一律锚回原词，见 sw-workflow/terms.md，不自创译名。
日本原创剧本的实战路径，来源《从零开始做编剧：10 位日本金牌导演、编剧谈剧本》（泊贵洋编）、《故事创作大师班·国际卷》（荒井晴彦）。同一大师班中的韩国（吴胜郁、崔石焕）与法国（奥比坦）编剧见 sw-korean-french-screenwriting。与好莱坞体系的关系：古泽良太、内田贤治、筧昌也承认三幕/起承转合是最有效结构但"探究好作品为何是三幕"；三木聪、园子温、横浜聪子、高桥泉、福田雄一走另一条路——主题后置、不写情节构想、片段联结、人物先于事件；行定勋把剧本当"坐标轴"和"议论的材料"。 小津安二郎的剧本范例见 ozu-screenplay-style；编者结语："不要依赖改编剧本，凭原创决胜负。"工作单与情节构想范例见 reference.md。
一、两派方法：结构优先 vs 人物/片段优先
| 结构优先派 | 人物/片段优先派 | |
|---|---|---|
| 代表 | 古泽良太、内田贤治、筧昌也 | 三木聪、园子温、横浜聪子、高桥泉、福田雄一、大宫艾丽 |
| 起点 | 题材指针、设定、"如果＋而且"、结尾 | 小素材笔记、演员、人物履历/日记、亲身经历 |
| 主题 | 动笔前确定或由题材带出 | 写到七八成时"无意间浮现"（留萌等待鲱鱼） |
| 情节构想 | 必写；先画框架/表格/A4 全集结构 | 不写或极简（"一写情节构想剧本就没爆发力"） |
| 代价 | 按结构写不一定有趣 | 想不出情节之间的衔接"简直身处地狱" |
编者："文科有文科的方式理科有理科的方式，右脑派依靠右脑左脑派依靠左脑。"选一条适合自己的路，但两派都同意：先写一部再说（三木"把玩具箱子翻过来，先写一部！"）；拿给别人看，被说"没意思"才有意义（园子温/福田）。
二、结构与节奏
- 三幕＝起承转合（古泽）：起厘清人物关系，承呈现矛盾冲突（"承"精彩就能写出好剧本，"承"多则变化多），转与合归并为高潮。摹写《七武士》剧本、给电视剧录像倒写成剧本是他的学习法。
- 主人公确定目标的瞬间＝情节点（内田）：《E.T.》把 E.T. 藏在家里；《虎胆龙威》拿起机关枪。以 30 分钟为段思考四段。大学老师："大家一定不要误认为按三幕剧结构创作就能创作出好作品，我们要探究的是好作品为何是三幕剧结构。"
- 先定结尾（内田）："不事先考虑目的地就来到机场"；园子温《爱的曝光》最初想到的也是两个场景（海边劝妹妹、精神病院妹妹来救）再倒推前半。
- 速度感与跳跃（古泽）：几个故事交错发展镜头不断转换产生速度感；无趣的场面＝没有跳跃感的场面，删除或加新想法使之重要；"一下子跳过两到三级"，上一场面与下一场面内容相反；台词后一句否定前一句；情节忽左忽右（《LOST》《福音战士》影响）。
- 尽早结束情况说明（三木）："在我的作品里情况说明部分会很快"；用"美禄"巧克力牛奶做"速成沼泽"的铺垫，2 分半 108 个镜头独白开场。
- 空转与扇动（三木）：吉列姆/《双峰》式"一边空转一边扇动"，"电影里多一些看似没用的空转才更有意思"。
- 10 分钟法则（福田/羽住）：电影 20 分钟电视剧 10 分钟内必须发生事件，让观众预知本集要发生什么。
- 电视剧实务（三木/古泽）：一卷（到广告）约 10 分钟，10 分钟内有 7 件事就列 7 条提纲并标广告点；在一张 A4 纸把全部剧集结构列出再写（第 2 集伏笔第 5 集起作用）；一个案件贯穿全剧的群像剧（《怪胎刑警》）；先画"必须预先呈现的顺序"框架；固定招数便于观看（木下部长每集拉面接待）。
- 不必给主人公目标／不必成长（三木）："人就必须得进步吗？傻瓜从头到尾都是傻瓜并没什么成长却因此有趣"；《废柴三人组》"一生都在过暑假"；《乌龟意外之速游》以《原野奇侠》为底（间谍朋友的离去），"什么也没发生的故事"。
- 反理论（横浜）："不均衡感应该会更有趣""如果照着理论去写作就不能产生超出别人想象的内容"；代价是衔接极难，先给制片人看构想。
- 重复日常中的偏离（行定）：小津式"既然来到这儿了就从这儿开始拍摄然后再将它重复"，樱花岔道、因他人变道——"剧本最为隐秘的韵味"；"首先我想描写的是重复的日常中不存在的丰富度"。
三、素材与构想
- 一天一条笔记（三木/横浜/筧）：记有趣/感兴趣的事，半年 180 条回看发现自己被什么吸引；写生簿涂鸦人物像＋关键词（古泽）；提纲软件（Acta/Tree）把笔记罗列重组成章节；"把玩具箱翻过来"倒出全部素材再排列找隐藏主题；福田相反："比起记笔记还是铭刻于心比较好"，笑料是记忆的游戏。
- "如果"＋"而且"（筧）：构想＝两件相去甚远之物的加法——"美女"＋"罐头"、"足球实况"＋"临死前的补时"、"置换房间"＋"前住户的恋人"＋"职业摔跤手搬家队"、"男性"＋"花样游泳"（《水男孩》）；"而且"能让偶然被认可，"进而"则令人扫兴；"如果"单独不够，混进不同内容才是切入点。福田："一定要有两个触发灵感的素材，只有一个会觉得有所欠缺。"
- 从题目开始（三木/古泽）：题目要让人想问"是什么事"（《速成沼泽》《爆裂城市》《铁男》）；"60 岁的情书"仅看题目就是全新的爱情故事；熟知的形式＋全新做法＝"假性既视感"（三木）；园子温：先把梗概讲给别人听没反应就放弃，《循环自杀》《爱的曝光》刚说出题目大家就笑。
- 分析"主要讲了什么事"（三木）：《原野奇侠》＝"遇见的人离去又回到平常生活"→《乌龟》；《教父》＝子承父业→"大便工场"；"不擅长创作故事的人可以试着以'主要讲了什么事'为线索去构想"。看老电影学结构；喜欢的类型看到底（园子温的恐怖片）。
- 一两句话概括（内田）：《洛奇》＝"一个三流拳击选手获得冠军挑战权与对手打成平局"；《放课后》＝"男子帮助初恋"；做不到一定是中间跑偏。
- 改变时间轴不花钱（内田）："任凭你怎么改变时间轴都不用花一分钱"——低成本电影的秘密武器；"普通的花瓶卖不出去，说'按住它会发光'或许就能卖"。
- 取材：园子温采访高中女生一个介绍一个（接发、流鼻血）；李沧东走路采风"开车就不像作家了"；筧采访家具设计师建筑师"正因为不虚构才能编造出异想天开的大大的谎言"；横浜遇熊放进最后镜头；行定的搅拌器金鱼"他跟谁一起去的来着"。
- 亲身经历是突破口而非照搬（横浜）："经历并不等于电影，要考虑如何把经历运用到电影中扩展故事"（粪坑、躲避球、断头事故、"神"）；园子温入邪教、逃到过激派据点"都怪食物"；荒井晴彦"你要做的就是把你害羞的事情暴露给别人"；三木"难为情的部分有很强的感染力"。
- 主题后置（三木/内田/园）：写到七八集才发现"这部剧的出场人物都在等待着什么"→留萌是等待鲱鱼的城市；《在池中》"没必要 3 个人全都被治愈"；名字改成"雀""孔雀"才看到突破口（幻想型）；主题一旦浮现就据此删多余镜头台词，"讨厌说教感"；一边写一边等关键词"慢慢来"。大宫相反：主题可由主人公在结尾说出（"休业是面向开业的准备时期"），承认"不高明"但有力；高桥："创作指针性的台词或镜头"作顶峰而非模糊主题。
四、人物
- 人物履历与日记（内田）：写主人公履历、剧中三天的日记（"这里逃跑太懦弱"→"骗过对方再逃"→反推伏笔）、想象"如果是同班同学"；"观众看到的仅仅是海面上露出的小岛，海面之下隐藏着一座像山一样庞大的'无用功'"。
- 人物经过酝酿熟成才形成"起"（园子温）：蹩脚作家在没想好人物时就考虑华美行文；只要角色有意思就让他抢主角戏（毕加索的背景压过花）。
- 设定决定人物（筧）：从设定逆推职业性格——罐头里爬出美女需要一个不怀疑的戏剧青年；临死补时需要有理由死的实事摄影师；"因为大雄没出息哆啦 A 梦才有价值"；固定形象＋反转（"看似认真实为坏蛋"）足够，"符号化是通向下一阶段的入口"。
- 人物＝演员＋缺点（福田）：先想演员在这部剧里能带来什么"好吃看得见"；从缺点开始（蜘蛛侠被女子看一眼就吐不出丝；蝙蝠侠无缺点故不爱）；八成优秀两成缺点；决定是"展示没出息"还是"提示其实优秀"；拼命努力（尤其拼命撒谎）令人喜爱；反派既坏又蠢（海盗三人组）。
- 不创作"角色"而写"人品"（高桥泉）："如果是学者就会说'房间里摆放着文献'，但我想的是'那里应该有两本《哆啦 A 梦》'"；关注人不关注事件；看人物发出的"热"（为逃职工旅行虚假预约 100 人）。
- 从外表反差造人物（三木）：地铁里盘腿的朋克青年给老奶奶让座→"格斯"；名字决定人物（雀/孔雀；木下"幸之助"；大宫"名字决定人物角色所以通常很慎重"）。
- 3 人组（三木）："1 对 1 很难判断哪种价值观正确情节也难转折，3 个人关系一旦变化情节便能与价值观一起转变"。
- 加入外来人员/局外人（古泽）：《外事警察》糊里糊涂被选拔的女警让观众看到组织多特殊；"卑鄙的英雄"。
- 边写边让人物出场（高桥）："正想着'小林老师不出现了'结果他就出场了，既然出现了那就让他做点什么"；福田"一边变换人物角色一边创作故事"，"我非常欢迎跑偏"。
- 像建花坛/备火锅食材配置人物（大宫）；对照人物（君岛部长 vs 木下部长）。
- 反派：园子温"没有人百分百坏"（韩国编剧的反派写法见
sw-korean-french-screenwriting）。
五、台词
- 来自与自己的内心对话（大宫）："为了探明自己的心情我使用了很多语言来表达"，"从一个小时或一个月的内心对话中产生的词句就变成了剧本的台词"；不参考歌词（会变成卡拉 OK 录像）；先定色调与拟声词（晚霞/砰）。
- 保留暧昧、重声音反响（横浜）："不知道是真是假"不同的人不同理解；"比起意思更重视声音的反响"；只讲发生的事不说"伤心"（除去情感）；"说出精神创伤"的长台词像诗。
- 先写台词再生成故事（福田）：确定人物后先写台词一边变换角色一边创作；"把捧哏的角色交给观众"对话才不中断（否则"逗了啊捧了逗了啊捧了"看了累）；三重逗哏"全员是笨蛋"对话也能继续。
- 真实台词（荒井）："你不要打我的脸，因为我是一个女演员"源自前女友；台词简洁趋势下更重要是写好一场场戏让"我爱你"因铺垫打动人。
- 改编台词（高桥）：漫画台词因有画依托才成立，影像化须重写；小说书面语须置换口语；不改意思另造台词；被动主人公变主动。
- 指针性台词（高桥）：以一句具体台词或镜头为顶峰扩大山脚的原野。
- 地方口音与口头禅（三木/大宫）：木下"该回去了""哪个都行""没什么，死不了"；《法尔戈》式拟声词参见
sw-american-case-studies。 - 台词朗读：写完出声读一遍或让人分饰模拟排演（韩法两种围读法见
sw-korean-french-screenwriting）。
六、喜剧与笑料（福田/三木/崔）
- 笑料体系：逗哏/捧哏/天然逗哏分配（《33 分侦探》大田原警部为"大逗哏"深信侦探、助手插话）；捧哏交给观众；固定形式（万年台词"让我用足 33 分钟"、每集移动镜头）留"看不见的捧哏"。
- 侦探说绝对不能说的话："这样那样就是这样那样！""双胞胎就是共犯！"——先断言再推进；借推理史伎俩加信息性。
- **现实感是什么？**福田："现实感从何而来？来自平时的生活吗？还是以前看过的电视剧？"——泼水→喷杀虫剂→急救员偷拍，从新闻从他人荒唐事扩大范围，"改变看法怀着爱问他为什么这么做"；"作家现实感范围狭窄绝不是引以为豪的事"。
- 哭点一个就够，笑点不止一个；100 名观众有一个没笑就想问"哪里没意思"。
- 三木"脱力系"：噱头优先于故事；主妇成为间谍；只下不上的楼梯；"黑 T 换白 T"丢失重要的东西——大的疏漏开始于微小的细节（《雌雄大盗》纵向停车）。
- 荒井："十个包袱观众感受三四个就不错，多抖"。
七、原创与改编、限制与合伙
- 原创从"状况"中诞生（行定）：服装商要模特穿衣→全员丧服的葬礼片；乐队歌词→烧教科书；香波广告→柴崎幸演坏女人三部；手机广告→临终影像；"确定好适合自己的束缚之后再去做，限制自由的内容反而会产生创新性；'请随便创作'最棘手"。内田："只允许用卷心菜和鸡蛋做料理更简单"；古泽"限制和不自由越强烈越能形成有趣的内容"。
- 适度差劲的剧本是好剧本（行定引鸭下信一）：有想象余地能让工作人员兴奋"我要做这个"；把可能删的也写进去问"有必要吗"，"剧本为议论而存在"；与编剧合伙"挣时间"（自述→他写→改不同处→换入好处）；"剧本由众多人去写精准度才会变高"。
- 剧本是坐标轴（行定）：电影"三回生两回死"（剧本→拍摄→剪辑），中轴不牢就不知以什么为目标；原创＝描写方法（北野武的省略）而非故事；不怕"有几分相似"、不怕肤浅。
- 改编心得（荒井/行定/高桥/理查兹）：站在评论者角度审视原著，"很喜欢的原著很难改编因为爱会让人麻木"；只保留题目也可以（《W 的悲剧》戏中戏套"龙套追梦"）；"自己以什么视点从小说里发现了什么"（伊藤千寻："往前迈一步就是一部电影"）；导演先告诉编剧哪部分打动了他；"改编时编剧不能知道太多"。三人执笔剪刀石头布认领前中后各写一周再串（荒井）。
- 职业观（古泽）：剧本是所有相关者"自己的作品"，认真对待要求，"专业人士就应是穿针引线般再创作"；先商业成功再新鲜感/社会影响/自我挑战；"写出能转化成金钱的剧本"；会修改是必备素质；创作"不专心看就看不懂"的作品；"制作的乐趣远大于观赏的乐趣"。
- 顽强意志（高桥）：新人一年 3–5 本每天 10 小时；拥有一生追求的主题（"痛苦"→温柔，钟摆先摆向痛苦）就什么都能写。
- 园子温："如果作品不能招致强烈的厌恶感……就不算真正的好作品"；"没有什么事是不能做的"（独白过多、4 小时、一小时后才出片头）；结构比作树：枝叶→树干→树根；先建结构写或"连载物"式虚张声势推进；"倾心于原创"——没有原著担保才新鲜。
- 韩法对照见
sw-korean-french-screenwriting（吴胜郁的卧底采风与"讲真话的说谎者"、崔石焕的类型承诺与两个反转、奥比坦的"对话放最后写"与意大利式围读）。
八、诊断清单
- 我是结构优先还是片段优先？选定后是否至少写完一部？
- 题目让人想问"是什么事"吗？梗概讲给三个人听反应如何？找到说"没意思"的人问"哪里"了吗？
- 构想是两件相去甚远之物的加法吗？用了"而且"而非"进而"吗？
- 结尾定了吗（哪怕先有一个画面）？"承"够多够精彩吗？每场有跳跃感吗？后一句台词否定前一句了吗？
- 情况说明是否尽早结束？10 分钟内有事件吗？电视剧一卷 10 分钟 7 件事列了吗？
- 人物：履历/日记写了吗？从设定逆推了职业吗？演员的缺点想好了吗？"人品"而非"角色"（房间里那两本《哆啦 A 梦》）？名字定了吗？
- 素材：一天一条记了吗？取材/亲身经历用作突破口而非照搬？害羞的事暴露了吗？
- 主题：是让它自己浮现（浮现后删多余）还是先定？有没有说教？有指针性台词或镜头吗？
- 喜剧：逗捧分配了吗？捧哏交给观众了吗？"现实感"是不是只来自你看过的剧？
- 限制：这次的束缚是什么（预算、场地、演员档期、委托条件）？把它当武器了吗？
- 剧本留了议论与改变的余地吗？工作人员看了会兴奋吗？
- 主人公一定要有目标/成长吗？不成长的版本是否更真？日常的重复与偏离写出来了吗？
九、工作流程（原创日式剧本）
- 玩具箱：倒出半年笔记；圈出"如果……"与最想拍的镜头/画面；找两个能相加的素材。
- 题目与一句话：写让人想问"是什么事"的题目；用一两句概括；讲给三个人听。
- 决定路径：结构优先→定结尾、画四框架/A4 全集表、情节构想；片段优先→写人物履历/日记、先写台词、"连载物"式推进。
- 人物：设定逆推职业；演员＋缺点；名字；外来人员/局外人；3 人组；对照人物。
- 情节构想（若写）：客观描写，写打动主人公的"事件"（微小亦可），不写"他这么想"；标起承转合；反转后回头补伏笔。
- 剧本：跳跃、否定式对白、尽早结束说明、空转扇动；台词来自内心对话与真实取材；保留暧昧。
- 读：念给苛刻的人听；找说"没意思"的人；主题浮现后删多余。
- 企画书（电视剧）：梗概／人物（口头禅座右铭视角人物对照人物）／前两集梗概＋各集标题／策划目的与看点＋类比作品——"原创必须比改编更通俗易懂"。
- 拍：独立电影定拍摄日期逼出剧本；缺钱按缺钱办；剧本留余地供议论；接受"电影会因演员而改变"。
© jtydhr88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in plugins/screenwriting/skills/sw-japanese-screenwriting of jtydhr88/screenwriting-skills.
- SKILL.md
- reference.md
Open the folder on GitHubat commit 51115f1
Compare with similar skills
Sw Japanese Screenwriting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sw Japanese Screenwriting this skilljtydhr88/screenwriting-skills | 1.6k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode | 7.4k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| InkOS Creative HarnessNarcooo/inkos | 10k | 1 repos | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Novel Arteternityspring/shuohao-skills | 4.3k | — | ~1.1k | Automated safety check: Notes | Apache-2.0 | |
| SepiaNanako0129/sepia | 3.1k | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Short Web Fiction Trend Scan
zenstory-ai/oh-story-claudecode
Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.
InkOS Creative Harness
Narcooo/inkos
Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.
Novel Art
eternityspring/shuohao-skills
给 AI 短剧出美术设定集（场景 + 叙事道具）：场景的设计意图、一致性锚点、光照时段变体、 空景提示词；道具的戏剧功能、状态变体、尺度参照、白底无手提示词。
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
Story Toolbox Router
zenstory-ai/oh-story-claudecode
Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.
More from jtydhr88/screenwriting-skills
All 25 skills in this repoOzu Screenplay Style
jtydhr88/screenwriting-skills
Writing screenplays in the style of Ozu Yasujiro and Noda Kogo (小津安二郎・野田高梧) — distilled from six complete screenplays (晚春 Late Spring, 麦秋 Early Summer, 东京物语 Tokyo Story, 浮草 Floating Weeds, 秋日和 Late…
Sw Story Structure
jtydhr88/screenwriting-skills
Story structure for screenplays and stage plays (故事结构) — merged from Syd Field's paradigm and plot points, Blake Snyder's Save the Cat beat sheet and board, Robert McKee's Story…
Chekhov Dramaturgy
jtydhr88/screenwriting-skills
Writing plays and screenplays in the Chekhovian mode (契诃夫戏剧法) — distilled from the complete plays (没有父亲的人/普拉东诺夫, 伊凡诺夫, 林妖→万尼亚舅舅, 海鸥, 三姊妹, 樱桃园, nine one-acts) plus Chekhov's own letters…
Succession Series Writing
jtydhr88/screenwriting-skills
Writing a Succession-style ensemble series (继承之战群像剧写法) — distilled from Jesse Armstrong's complete shooting scripts for all four seasons, 39 episodes (Faber 2023), with his introductions and…
Sw American Case Studies
jtydhr88/screenwriting-skills
Case studies of American screenwriting (美国电影剧作案例) — Mei Feng's readings of the Hollywood Western (value pairs, four oppositions), screwball comedy (strong heroine, buddy vs adversary two-hander)…
Sw Character Conflict
jtydhr88/screenwriting-skills
Character creation, protagonist/antagonist design and dramatic conflict for scripts (人物/对手/冲突) — merged from Lajos Egri (three-dimensional character, orchestration, unity of opposites, pivotal…
Related
Categories
Questions about Sw Japanese Screenwriting
What does Sw Japanese Screenwriting do?
Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida…. Sw Japanese Screenwriting is an agent skill from jtydhr88/screenwriting-skills.
When should I use Sw Japanese Screenwriting?
Sw Japanese Screenwriting fits situations like: writing an original Japanese-style script; working from small material and fragments; choosing between structure-first and character-first methods; building a Japanese 企画書.
How do I install Sw Japanese Screenwriting in Claude Code?
Run `npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a claude-code`. Or copy the skill folder (plugins/screenwriting/skills/sw-japanese-screenwriting in jtydhr88/screenwriting-skills) into .claude/skills/sw-japanese-screenwriting in your project. Claude Code loads it when a task matches its description.
How do I install Sw Japanese Screenwriting in Codex?
Run `npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a codex`. Or copy the skill folder (plugins/screenwriting/skills/sw-japanese-screenwriting in jtydhr88/screenwriting-skills) into .agents/skills/sw-japanese-screenwriting in your project. Codex loads it when a task matches its description.
Can I use Sw Japanese Screenwriting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jtydhr88/screenwriting-skills --skill sw-japanese-screenwriting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sw-japanese-screenwriting, .gemini/skills/sw-japanese-screenwriting, .github/skills/sw-japanese-screenwriting and .opencode/skills/sw-japanese-screenwriting in your project.
What does Sw Japanese Screenwriting need to run?
SKILL.md names no scripts, command-line tools or credentials: Sw Japanese Screenwriting is instructions for the agent only.
Does Sw Japanese Screenwriting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sw Japanese Screenwriting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Sw Japanese Screenwriting use?
Sw Japanese Screenwriting is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sw Japanese Screenwriting use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sw Japanese Screenwriting?
Skills that share tags, products or a category with Sw Japanese Screenwriting: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Creative Harness (Narcooo/inkos, 10k stars) and Novel Art (eternityspring/shuohao-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sw Japanese Screenwriting?
jtydhr88 (a GitHub user) maintains it in jtydhr88/screenwriting-skills, which has 1,621 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 3, 2026.
Source: jtydhr88/screenwriting-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.