CtrlK
BlogDocsLog inGet started
Tessl Logo

director-visual-language

Use for requests that need strong cinematic taste, directing logic, camera language, lighting strategy, lens intent, composition, and premium visual tone.

65

Quality

78%

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/director-visual-language/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 lean, well-structured instruction skill that delivers concrete prompting phrasings and a clear decision checklist without padding, and its single-task scope with no bundle files satisfies the simple-skill allowances for workflow clarity and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and tightly organized with no concept explanations Claude already knows and no padding — every section (Goals, Translate Style Into Decisions, Cinematic Rules, Prompting Heuristics, Consistency Rules) earns its tokens.

3 / 3

Actionability

As an instruction-only skill it gives concrete, copy-paste-ready phrasings ("low-angle medium close shot with compressed perspective", "harsh backlight with near-silhouette separation and red edge flare") plus an explicit decision checklist and a clear avoid list.

3 / 3

Workflow Clarity

This is a single-task heuristic skill with no destructive or batch operations, so the unambiguous decision checklist in "Translate Style Into Decisions" with its enumerated framing/angle/lens/movement/lighting/palette/texture fields satisfies the simple-skill bar for clarity.

3 / 3

Progressive Disclosure

At ~43 lines with no external references needed, the well-organized section headers provide clean navigation meeting the under-50-lines/no-references bar for progressive disclosure.

3 / 3

Total

12

/

12

Passed

Description

57%

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 establishes a clear, distinctive niche with explicit use-when guidance, but it foregrounds trigger domains over the concrete actions the skill performs and mixes natural user terms with internal jargon.

Suggestions

Lead with what the skill does, e.g. "Translates style requests into concrete camera, lens, lighting, composition, and motion decisions" before the use-when clause.

Replace skill-internal phrasings ("lens intent", "directing logic", "premium visual tone") with terms users actually say ("cinematic look", "shot framing", "movie-style lighting").

Ensure the description explicitly answers both what and when, keeping the existing "Use for requests that need..." trigger.

DimensionReasoningScore

Specificity

The description names a specific, well-scoped domain ("cinematic taste, directing logic, camera language, lighting strategy, lens intent, composition, and premium visual tone") but lists no concrete actions the skill performs — it says when to invoke rather than what it does.

2 / 3

Completeness

The "when" is explicit ("Use for requests that need...") but the "what" is only implied — it never states the skill translates style into concrete camera/lens/lighting decisions, so one half of what+when is missing.

2 / 3

Trigger Term Quality

Relevant natural terms appear ("cinematic", "camera", "lighting", "composition", "directing") but are mixed with skill-internal jargon like "lens intent", "directing logic", and "premium visual tone", and common user phrasings are not broadly covered.

2 / 3

Distinctiveness Conflict Risk

The cinematic directing/visual-language niche is clearly distinct with domain-specific triggers unlikely to fire for unrelated skills.

3 / 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.