CtrlK
BlogDocsLog inGet started
Tessl Logo

inkos-storyboard

剧本与叙事文本到可拍、可画、可生图分镜的视觉拆解方法。Used for storyboard and image-prompt production.

56

Quality

63%

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 ./packages/core/skills/inkos-storyboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 concise and reasonably actionable with a clear enumerated checklist of required shot/prompt elements, but it lacks an explicit sequenced workflow with checkpoints and fails to point to the available reference file.

Suggestions

Link the existing reference, e.g. under a continuity bullet: "See [references/shot-continuity.md](references/shot-continuity.md) for continuity tracking details."

Add a short numbered workflow (beat → shot list → continuity check → image prompts → review against constraints) to make the sequence explicit.

Include one compact worked example (a beat turned into a shot + a generation-ready image prompt) to lift actionability.

DimensionReasoningScore

Conciseness

The body is a lean set of tight bullets with no padding and no over-explanation of concepts Claude already knows; every line is task-specific guidance that assumes competence.

5 / 5

Actionability

Concrete, specific guidance enumerates what each shot and image prompt must contain (dramatic purpose, visual subject, action, spatial relation, shot size, continuity), but no worked example of a finished shot breakdown or image prompt is provided.

4 / 5

Workflow Clarity

The bullets imply a conceptual sequence (translate beats → define shot elements → preserve continuity → refine → build prompts → separate layers → respect constraints), but steps are not explicitly sequenced and there are no validation checkpoints; this is not a destructive/batch operation so the hard cap does not apply.

3 / 5

Progressive Disclosure

The body is well-organized as an overview, but the existing references/shot-continuity.md is never linked or signaled from the body, so navigation to the deeper material is missing.

3 / 5

Total

15

/

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 clearly states a niche capability with relevant bilingual trigger keywords, but its "when to use" guidance is weakly implied rather than an explicit trigger clause, leaving completeness and trigger coverage mid-range.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for storyboards, shot breakdowns (分镜), or image-prompt generation from a script or narrative."

Broaden trigger terms with common synonyms users say (e.g. "shot list", "storyboard panels", "分镜表").

Spell out a few concrete actions (e.g. decompose beats into shots, draft generation-ready image prompts, track continuity) to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ("剧本与叙事文本到...分镜的视觉拆解方法") and 1-2 concrete actions (visual breakdown into storyboards, image-prompt production), but does not list multiple specific actions for comprehensive coverage.

3 / 5

Completeness

The "what" is clear (visual breakdown method), but the "when" is only weakly implied via "Used for storyboard and image-prompt production" rather than an explicit "Use when..." trigger clause, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Relevant bilingual keywords are present ("storyboard", "image-prompt", "剧本", "分镜", "叙事文本"), but common variations and synonyms (e.g. "shot list", "storyboard shots", file extensions) are missing.

3 / 5

Distinctiveness Conflict Risk

It targets a distinct niche (script-to-storyboard / image-prompt production) with specific triggers, with only minor overlap risk against general image-generation skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Narcooo/inkos
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.