CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cinematic-storyboard

专业镜头设计与动作接点,把叙事重点、画面焦点和物理状态落实为可审阅镜头契约。

56

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./ruoyi-modules/ruoyi-chat/src/main/resources/short-drama/skill-catalog/cinematic-storyboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a compact, well-structured rulebook for a complex multi-phase workflow: it defines a precise shot_design contract, explicit cut-point and physical-state continuity rules, and review checkpoints with feedback loops. Main gaps are the absence of a complete worked output example, minor cross-section repetition, and no pointer to the bundled reference file.

Suggestions

Add one complete worked example (a short scene_plan summary plus two adjacent panels with fully populated shot_design including state_in/state_out and cut_in/cut_out) so the field contract is unambiguous in assembled form.

Consolidate the repeated fixed-shot-count/no-preset-length constraints into a single stated rule instead of restating them in the planning, review, and save sections.

Add a one-line pointer to references/libtv-sources.md (e.g. in a 来源/出处 section) so the bundled reference file is discoverable from the body.

DimensionReasoningScore

Conciseness

The body is dense rule-carrying prose with no padding and no explanation of concepts Claude already knows — every line encodes a domain-specific constraint or contract rule. It is not a 5 because a few constraints are restated across sections (e.g. "不预设片长" / "不追求固定数量" / "不按固定镜数...判定" recur in the planning and save sections) and could be consolidated.

4 / 5

Actionability

The guidance is highly concrete for an instruction-only skill: a 12-field shot_design contract with per-field semantics, enum values ("opening / continuous / time_change / space_change"), example state keys ("匠人.悬挂姿态", "布翼.倾角"), an incremental state_delta contract, and a worked micro-example (门闩卡住、抬闩、推开门). Not a 5 because there is no complete worked example of a scene_plan/panel output showing the fields assembled together.

4 / 5

Workflow Clarity

Sections follow the actual pipeline (叙事和镜头设计 → 按原文规模规划生成段 → 跨镜契约 → 细化和首帧 → 审阅 → 媒体提示词 → 审阅建议与保存), and the 审阅 section defines explicit checks (focus occupying frame, contact visibility, "上一镜末态是否等于下一镜首态") with feedback loops ("先修对应镜", "真实结果不符时进入对应镜头复核"). Not a 5 because the sequence is implicit in section order rather than explicitly sequenced with a step list or per-phase validation checklist.

4 / 5

Progressive Disclosure

The ~65-line body is cleanly sectioned with each phase getting its own focused section, and no content that should be split out is inlined. Not a 5 because the bundle contains references/libtv-sources.md which the body never mentions or links to — a minor navigation gap, even though that file is provenance material rather than operational content.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a specific, domain-appropriate capability but reads as a compressed design statement rather than a trigger-friendly skill description. It completely lacks "when to use" guidance and misses the most natural trigger terms (notably 分镜/storyboard).

Suggestions

Append an explicit trigger clause, e.g. "Use when planning, refining, or reviewing storyboard/分镜 output for AI video generation, or when the user mentions 镜头设计, 分镜, shot design, or video shot planning."

Include natural synonyms users would actually say — 分镜, storyboard, 视频生成, 镜头规划 — alongside the current terminology.

List the concrete deliverables (scene_plan 摘要, panels with shot_design 契约, 首帧参考) so the "what" covers multiple specific actions instead of one composite action.

DimensionReasoningScore

Specificity

The description names the domain ("专业镜头设计与动作接点") and 1-2 concrete actions ("把叙事重点、画面焦点和物理状态落实为可审阅镜头契约"), which matches the anchor for naming a domain with a couple of concrete actions. It is not a 4/5 because it does not list several distinct specific actions, and not a 2 because the actions it names are concrete rather than generic.

3 / 5

Completeness

The "what" is clearly stated (design shots and action cut-points, produce reviewable shot contracts), but there is no "Use when..." or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not a 2 because the "what" is clear and specific rather than vague.

3 / 5

Trigger Term Quality

"镜头设计" and "镜头契约" are relevant domain keywords, but the most natural user phrasing for this domain ("分镜"/storyboard, "视频生成", no file extensions or synonyms) is missing. Some relevant keywords without common variations matches the 3 anchor; not a 2 because the terms present are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

The niche (shot-design contracts with physical-state continuity for video generation) is specialized and unlikely to trigger the wrong skill. Not a 5 because the absent trigger phrasing leaves minor overlap risk with generic video/photography/prompting skills rather than clearly distinct triggers.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ageerle/ruoyi-ai

Path

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

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.