shot-size-and-angle-language

Use for requests that need precise shot-size vocabulary, angle selection, narrative framing logic, and coverage phrasing for storyboards and prompts.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 tight, well-structured reference that adds only what Claude would not already know and gives concrete selection guidance. It is an exemplar of a lean single-purpose skill.

Dimension	Reasoning	Score
Conciseness	Lean abbreviation tables and terse mapping rules ('ECU/CU for micro-expression...') assume Claude's competence with no redundant explanation; every token earns its place.	3 / 3
Actionability	Gives concrete, specific mappings from shot-size and angle to narrative meaning plus explicit coverage rules ('Change shot size to change information priority'), which is actionable instruction guidance without needing code.	3 / 3
Workflow Clarity	A single-purpose reference skill with an unambiguous usage; per the simple-skills note, no multi-step validation sequence is required, so workflow clarity earns a full score.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, yet well-organized into clearly labeled sections (Standard Vocabulary, Selection Rules, Angle Rules, Coverage Rules), satisfying the simple-skills exception.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 occupies a clear niche, but its trigger guidance is abstract and lacks common natural-language variations a user would actually say. Strengthening the 'when' clause with concrete user-facing situations would lift completeness and trigger-term quality.

Suggestions

Add concrete triggering situations to the 'when' clause, e.g. 'Use when the user asks for a shot list, storyboards, shot breakdowns, or coverage for a scene.'

Expand natural trigger keywords to include common variations users say: 'framing', 'camera angle', 'shot list', 'shot breakdown', 'coverage'.

Lead with a clear declarative 'what' statement before the trigger clause so the capability is stated independently of the 'when'.

Dimension	Reasoning	Score
Specificity	Names the domain plus four distinct concrete capabilities ('shot-size vocabulary, angle selection, narrative framing logic, and coverage phrasing'), matching the multiple-specific-actions anchor.	3 / 3
Completeness	It has an explicit 'Use for requests that need...' trigger and implies the 'what' through the capability list, but the when-trigger is abstract ('requests that need precise...') rather than concrete user-facing situations, leaving 'what' implied within the trigger.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('shot-size', 'angle', 'storyboards', 'prompts') but omits common variations users would say like 'framing', 'camera angle', 'shot list', or 'coverage'.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (cinematography/storyboarding framing vocabulary) with distinct triggers, unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nolanx-ai/nolanx.ai
Path: .nolanx/skills/shot-size-and-angle-language/SKILL.md
Commit: 595d863

Reviewed: about 11 hours ago

Table of Contents

Discovery Implementation Validation

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.