CtrlK
BlogDocsLog inGet started
Tessl Logo

lighting-continuity-design

Use for lighting mood design, contrast control, shot-to-shot lighting continuity, and visual tone consistency across sequences.

62

Quality

73%

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 ./.nolanx/skills/lighting-continuity-design/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 tight, actionable set of lighting-continuity heuristics well-organized into focused sections with no padding. Its main gap is the absence of an explicit verification step for confirming continuity across shots.

DimensionReasoningScore

Conciseness

Lean bullet-point guidance with no padding and no explanation of concepts Claude already knows; every section (ratio heuristics, rules, prompting, failures) earns its tokens; not level 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Concrete, actionable guidance for an instruction-only skill: specific ratio bands (1:1–2:1, 4:1, 8:1+) with moods, a concrete attribute list to track (key direction, fill, rim, practical motivation), and explicit prompting directives and failure patterns to block; not level 2 because the directives are specific and copy-ready rather than abstract.

3 / 3

Workflow Clarity

The heuristics, rules, prompting, and failure lists imply an apply-then-check flow, but there is no explicit sequence or verification checkpoint for confirming continuity holds across shots; not level 3 because no validation/feedback loop is stated, and not level 1 because the guidance is organized and sequenced implicitly.

2 / 3

Progressive Disclosure

Under 50 lines with no external references needed ("StudioBinder lighting ratio guide" is a citation, not a bundle path) and well-organized into clear sections; per the simple-skills note this scores 3 with well-organized sections and no nested references.

3 / 3

Total

11

/

12

Passed

Description

60%

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 is specific and domain-focused with an explicit "Use for" trigger, but it merges the what and when into one clause and leans on compound jargon rather than natural user terms. It is solid but not maximally clear or distinctive.

Suggestions

Split into a distinct action statement plus a trigger clause, e.g. "Designs lighting mood and contrast... Use when planning shot-to-shot lighting continuity or visual tone across a sequence."

Add simpler natural trigger terms users would actually say (e.g. "lighting", "mood", "contrast", "continuity") alongside the compound phrases.

Sharpen distinctiveness by naming the sequence/shot context explicitly to reduce overlap with generic color or image-design skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "lighting mood design, contrast control, shot-to-shot lighting continuity, and visual tone consistency" — rather than vague language; not the level 2 anchor because it enumerates several specific actions, not just a domain and a few.

3 / 3

Completeness

The single "Use for ..." clause gives explicit trigger guidance (when) with the capabilities embedded as the what, but there is no distinct action statement of what the skill does separate from the trigger; not level 3 because what and when are merged rather than clearly both answered.

2 / 3

Trigger Term Quality

Relevant domain terms (lighting, mood, contrast, continuity) appear, but they are bundled into compound technical phrases ("shot-to-shot lighting continuity", "visual tone consistency") rather than the simple natural variations a user would say; not level 3 because coverage of plain user phrasings is incomplete.

2 / 3

Distinctiveness Conflict Risk

The lighting-continuity niche is fairly specific, but "contrast control" and "visual tone consistency" could overlap with broader color-grading or general image-design skills; not level 3 because some overlap with adjacent visual skills remains.

2 / 3

Total

9

/

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

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.