CtrlK
BlogDocsLog inGet started
Tessl Logo

storyboard-breaker

分镜拆解专业规范

59

Quality

68%

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 ./skills/storyboard_breaker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 well-structured, actionable instruction skill with a concrete field schema, a worked prompt-format example, and a clear sequenced workflow. Its main gap is the absence of an explicit validation checkpoint around the batch save step.

Suggestions

Insert an explicit verification step in 使用步骤 after save_storyboards, e.g. confirm scene_id values exist in the returned scenes and character_ids are within the allowed role list before finalizing.

Add a brief feedback loop for save/update failures (review error → fix fields → re-save), mirroring the validation pattern expected for batch operations.

DimensionReasoningScore

Conciseness

The body is lean and instructional, defining the shot-element schema and rules without explaining concepts Claude already knows; nearly every line is task-relevant, with only minor redundancy (时长 restated in 拆解原则 and element 11), matching the 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete executable guidance: named tool calls (read_storyboard_context, save_storyboards, update_storyboard), an explicit 17-field schema, and a fully worked video_prompt tagged-format example that is effectively copy-paste ready.

3 / 3

Workflow Clarity

使用步骤 provides a clear 5-step sequence, but the batch save (save_storyboards 一次性保存完整分镜) has no explicit validation/verification checkpoint, which per the guidelines caps workflow clarity at 2 for batch operations.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the content is self-contained and organized into clear, well-labeled sections (拆解原则, 镜头要素, 使用步骤, association/binding rules, quality), satisfying the 'well-organized sections with no external references' standard.

3 / 3

Total

11

/

12

Passed

Description

50%

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 identifies a clear niche but is essentially a terse title: it names the domain and core action without concrete capabilities, trigger variations, or an explicit use-when clause. It is functional but under-specified for reliable skill selection.

Suggestions

Add an explicit trigger clause, e.g. 'Use when 拆分分镜、生成分镜脚本、或为视频生成拆解镜头'.

Enumerate concrete actions (e.g. 读取剧本上下文、拆解镜头、生成 image/video/bgm 提示词、保存分镜) instead of the filler '专业规范'.

Include natural trigger variations such as 分镜脚本、镜头拆分、storyboard to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description '分镜拆解专业规范' names the domain and a core action (storyboard breakdown), but appends the filler term '专业规范' and lists no concrete enumerated actions, so it sits between the vague and comprehensive anchors rather than reaching the multiple-specific-actions level.

2 / 3

Completeness

It conveys a WHAT (storyboard breakdown) but includes no 'Use when…' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'分镜拆解' and '分镜' are relevant natural terms a user might say, but the description offers only this single phrasing with no common variations (e.g. 分镜脚本, 镜头拆分, storyboard), matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Storyboard breakdown is a fairly specific niche unlikely to conflict with unrelated skills, but the terse description lacks explicit triggers that would reliably distinguish it from adjacent video/shot-planning skills, landing at the 'somewhat specific but could overlap' anchor.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (8 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository
chatfire-AI/huobao-drama
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.