cinematic-storyboard

cinematic-storyboard is a skill for Claude Code, Codex from ageerle/ruoyi-ai. It costs 37 tokens per session (2,403 once invoked), scanned A, original, MIT.

A storyboard-planning guide for turning a script into reviewable video-shot plans. It connects each shot to the story event, visual focus, movement, space, and physical result.

In plain words
What is it for?
Use it to plan and review storyboard panels, divide scenes into natural video segments, choose camera positions and focus, and preserve actors, props, lighting, movement, and spatial relationships across shots.
Why use it?
It removes guesswork about what each shot should show and prevents extra clips, unfocused camera moves, or broken continuity. It also keeps shot planning tied to the script instead of imposing a fixed number of shots.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan and review storyboard panels, divide scenes into natural video segments, choose camera positions and focus, and preserve actors, props, lighting, movement, and spatial relationships across shots.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ageerle/ruoyi-ai/cinematic-storyboard
About the project

RuoYi AI is a full-stack enterprise platform for building AI assistants and agents that combine language models, knowledge bases, visual workflows, and multiple cooperating agents. Developers and organizations use it to manage model providers, retrieve information from documents, connect tools through MCP, and orchestrate agent workflows. The catalogue includes skills for working with RuoYi AI.

ageerle/ruoyi-ai · 5,756 stars · on GitHub · doc.ruoyiai.chat

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ageerle/ruoyi-ai --skill cinematic-storyboard
Clone the repo
git clone --depth 1 https://github.com/ageerle/ruoyi-ai

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cinematic-storyboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/ageerle/ruoyi-ai/cinematic-storyboard/github.svg)](https://agentmods.dev/skills/ageerle/ruoyi-ai/cinematic-storyboard)
Your own site
<a href="https://agentmods.dev/skills/ageerle/ruoyi-ai/cinematic-storyboard"><img src="https://agentmods.dev/badge/skills/ageerle/ruoyi-ai/cinematic-storyboard/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cinematic-storyboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/ageerle/ruoyi-ai/cinematic-storyboard"><img src="https://agentmods.dev/badge/skills/ageerle/ruoyi-ai/cinematic-storyboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,403 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.02403
Opus 5.5 $0.00015 $0.00961
Sonnet 5.5 $0.00007 $0.00481
Haiku 4.5 $0.00004 $0.00240

Measured 12d ago against content hash b2f90e00d6eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cinematic-storyboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

ruoyi-modules/ruoyi-chat/src/main/resources/short-drama/skill-catalog/cinematic-storyboard/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

专业分镜:先决定观众获得什么,再决定如何拍

只在分镜规划、细化和审阅阶段应用。剧本创作阶段只交付剧本;不另外生成摄影规则或摄影指导。保持项目实际演员、道具、风格、画幅与模型接口,不套别的作品或平台模型。

叙事和镜头设计

从原文提取一条可见的触发—应对—结果链。每个生成段围绕一个主要事件,段内摄影子镜头各自选择当前必须读懂的信息中心:具体的人、动作接触点、物件变化或空间关系。触发和回应可以在同一段连续表达,不因信息中心变化就另建生成任务。衣料、发丝、云雾与背景声服务主动作,不能抢走焦点。必须说明本段让观众新知道什么;仅换背景、重述外观或反复滑翔不能自动成为独立生成段。

先建立行为发生的空间和关系,再收紧到承担信息的局部。景别变化必须由关注目标变化引发,不按固定循环远—中—近,也不强制每镜变景别。局部镜保留可辨识的空间参照;动作镜中需要看清受力或接触结果时,不把它裁在画外。表情特写须由已经可见的事情触发。

机位、摄影轴线和人物身体朝向分别确定。跟拍锁人物相对画面位置,背景运动证明位移;推进用于发现细节,拉远用于揭示关系,固定机位用于让变化自己发生。每个摄影选择写具体信息目标;“电影感、缓推、环绕”不能独立解释拍法。整体光源方向和运动方向跨镜保持。

按原文规模规划生成段

先预演原文的有效动作与对白,再估算时长和适合内容的生成段数;用户未写时间时也按内容自然长度结束,不预设片长,不要求填写时间或镜数。段落安排与摄影设计在同一次请求中完成,不另加预估调用;镜数随原文内容、观看重点和表演节奏自然变化,不追求固定数量。

先输出简短的scene_plan制作摘要,确认核心事件、大致表演时间和段落安排,再展开panels。段落安排中camera_beats是拍法,不是另外的生成任务。估时参考真实对白、动作与必要停顿;原文字数仅帮助把握内容规模,外貌、材料、光色等并行描述不能折算为额外播放时间。摘要用于指导本次创作,不是保存前按镜数拦截的条件。

每个panel就是后续提交视频的一个生成段,不在segment内另列多个panel。先按原事件的因果、对白和动作容量安排连贯表演,再选择自然分段;不按总秒数除以段长硬算镜数。段内可用有动机的摄影切点转移关注,不增加生成任务。同一事件的触发—应对—结果优先连续演完,听者反应可与对白同框同步发生,不同人物可在同段依次说话。主剧情职责和表演阶段用于组织段内内容,不是必须逐项拆镜的清单。短描述的一次操作与可见结果可以连贯完成,也可按观看重点自然分段;多事件和长对白按真实容量规划,不套固定镜数。

划段前,先把维持同一目标的动作归到一个核心事件。例如门闩卡住、抬闩、推开门是一段操作;起始状态、发现问题、应对、恢复都服务这次操作,不各自领取一段时长。环境和外形在动作发生时同时呈现,建立空间不必先停留数秒;恢复后的姿态作为操作末尾的落点,不再单独延长一段。逐段写boundary_reason,说明叙事变化、观看重点或表演节奏为何适合在这里划段;段内也可以换摄影角度,不机械为每次换角度创建任务。展开panels前,在本次规划内合并仍能连贯完成的相邻安排,不另发一次修复请求。

保持原事件规模。人物、材料、构图、受力和声音可精细描写,但与原动作并行,不增加时长;不凭空添加准备出发、试探、失败重试、解释性对白、重复反应或无结果空镜。

跨镜契约

先选切点,再写起始构图规划。首帧是可选参考,用户需要时才制作,不是视频前置步骤。每一对相邻镜头必须明确前镜动作停在哪个阶段、下一镜从该阶段如何继续,以及为什么此刻切镜。持续动作不能在下一镜从头重做;完成结果不能在下一镜无因撤销。不能用叠化、风声或“接上”掩盖人物姿势、手持状态、道具连接或运动方向突变。

同一连续事件必须传递具体物理状态:人物承托/站坐姿态、手与物件的接触、关键道具状态、身体朝向、光源与运动方向。即使局部构图将身体裁在画外,世界状态仍保留。机位变化不等于人物改变姿势。若确实跳时/换地,标明过渡类型和原文依据,不能凭空添加换姿态过程。

镜头规划增加 shot_design 对象;它是同一规划的镜头契约,不是独立摄影任务:

  • focus:本生成段的主要事件或动作关系;段内子镜头的当前画面重点随事件推进转移。
  • viewer_gain:观众获得的新信息;与 story_result 对应。
  • framing:景别、机位高度/角度、前中后景和关注点位置。
  • axis:摄影机所在轴线一侧和屏幕运动/视线方向。
  • movement:实际主运镜或固定机位。
  • motivation:该构图/运镜如何让本镜信息更清楚。
  • transition:opening / continuous / time_change / space_change;同一事件默认 continuous。
  • cut_in:本镜开始的具体动作接点。continuous 镜逐字复制前镜 cut_out。
  • cut_out:本镜结束的具体动作接点;结尾写明确的收束状态。
  • state_in / state_out:非空 JSON 对象,键是当前事件稳定的“对象.属性”,值是简短文字。可选属性由题材决定,例如“匠人.悬挂姿态”“匠人.右手接触”“布翼.倾角”“飞行.屏幕方向”。持续事件内 state_in 逐项复制前镜 state_out,随后只在 state_out 修改本镜确实发生变化的属性。首末态不可只写“承接上一镜”“继续”“不变”。

Read the full file on GitHub · 71 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 71 lines · 37 tokens per session scan A b2f90e00d6eb

Subscribe to this mod's changes

cinematic-storyboard is a skill published in the GitHub repository ageerle/ruoyi-ai (5,756 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 2,403 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.

Related

Other skills, from other repositories

wegent-knowledge

Knowledge base management and search tools for Wegent. Provides capabilities to list, create, update, and search knowledge bases and documents using RAG retrieval. Use this skill when the user wants to manage knowledge bases, documents, or search for information programmatically.

wecode-ai/Wegent · 51 tokens

knowledge-org

A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.

bojieli/ai-agent-book · 96 tokens

rag-pipeline

A guide to RAG, a method where a system retrieves relevant passages from an external knowledge base before an AI model writes an answer. It covers splitting documents, searching by meaning or exact words, combining results, and measuring retrieval quality.

bojieli/ai-agent-book · 125 tokens

memory-rag-poisoning-detection

Detect persistent-memory poisoning and RAG/knowledge-base contamination via dialogue testing. Use when the agent has long-term memory, a user/preference store, or writes to a retrievable knowledge base.

Tencent/AI-Infra-Guard · 48 tokens

beautiful-article

A tool for turning source material—such as a web page, PDF, DOCX, Markdown file, text, screenshot, or pasted content—into a single offline HTML article.

ConardLi/garden-skills · 226 tokens

web-design-engineer

Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…

ConardLi/garden-skills · 96 tokens