CtrlK
BlogDocsLog inGet started
Tessl Logo

storyboard-shot-design

Use for shot-by-shot planning, storyboard generation, camera coverage, blocking, and precise visual sequencing for multi-shot videos.

66

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A tight, well-organized instruction-only skill: dense domain heuristics (camera-movement-to-emotion mappings, coverage rules, continuity anchors) with no token waste. The only gaps are the absence of a worked shot example and an explicit step order / final self-check.

DimensionReasoningScore

Conciseness

Lean bullet structure throughout with zero padding: every line delivers domain-specific guidance Claude would not generate on its own (e.g. 'Use orbit for transformation, awe, or unstable identity'), and no concepts Claude already knows are explained.

5 / 5

Actionability

The Per-Shot Template gives eight concrete fields to define per shot and the Coverage Rules are checkable constraints ('Each new shot must add either new information, stronger emotion, or clearer action'), but there is no worked example of a filled-in shot to anchor the template.

4 / 5

Workflow Clarity

The section order (template, coverage, camera logic, sequencing, failure cases) implies a coherent process and the single action is fairly unambiguous, but no explicit order of operations or self-check step (e.g. 'review the failure list against your draft') is stated.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into six clear, well-scoped sections, which satisfies the simple-skill guideline for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

75%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.

A solid, domain-focused description that names several concrete capabilities with natural trigger terms and clear niche separation. Its main weakness is the 'when' side: it opens with 'Use for' but never gives explicit 'use when the user mentions...' trigger phrases, and it omits common synonyms like 'shot list'.

Suggestions

Add an explicit trigger clause naming user-facing phrases, e.g. 'Use when the user asks for a storyboard, shot list, shot breakdown, or camera plan for a multi-shot video.'

Include common synonyms such as 'shot list', 'scene breakdown', and 'shot planning' to broaden natural keyword coverage.

Name the concrete output artifact (e.g. 'produces a shot-by-shot list with framing, camera movement, and continuity notes') to sharpen the 'what' side.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('shot-by-shot planning, storyboard generation, camera coverage, blocking, and precise visual sequencing'), but 'precise visual sequencing' is abstract and the concrete output artifact (a shot list / storyboard) is never named, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

'Use for...' provides equivalent explicit trigger guidance (so the missing-trigger cap does not apply) and the capability list answers 'what', but the 'when' side lacks concrete 'use when the user asks for / mentions...' trigger phrases, keeping it below the anchor-5 example.

4 / 5

Trigger Term Quality

Contains natural domain terms users would say ('storyboard', 'shot-by-shot', 'camera coverage', 'blocking', 'multi-shot videos'), but misses common variations such as 'shot list', 'scene breakdown', or 'storyboard panels'.

4 / 5

Distinctiveness Conflict Risk

'blocking', 'camera coverage', and 'multi-shot videos' carve a distinct niche with domain-specific triggers; only minor overlap risk with generic video-generation or videography skills.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nolanx-ai/nolanx.ai
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.