frame-light-leak-cinema

Film light leaks, grain, 16:9 letterbox, and large serif type for cinematic openings or chapter cards.

Quality

82%

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

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 lean, highly actionable visual spec that assumes Claude's competence and organizes a single-purpose template into clear layered sections. The main gap is the absence of a complete copy-paste HTML example and an explicit verification step.

Dimension	Reasoning	Score
Conciseness	The body is dense and spec-like with concrete values (hex codes, px, opacity, blend modes, font sizes) and no padding explaining concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Highly actionable with specific CSS values and inline snippets ("radial-gradient(ellipse at top right, #ffb547 0%, transparent 50%)", "mix-blend-mode: overlay"), but it stops short of a complete copy-paste HTML scaffold.	4 / 5
Workflow Clarity	A clear layered build sequence (canvas -> background -> text -> extras -> design details) with a constraints/forbidden checklist and a prefers-reduced-motion note, but no explicit validation checkpoint for the produced frame.	4 / 5
Progressive Disclosure	Under 50 lines with no external bundle files, yet well-organized into clearly signaled sections (【画布】, 【背景】, 【文字】, 【可选附加】, 【设计细节】), meeting the simple-skill exception for full marks.	5 / 5
	Total	18 / 20 Passed

Description

78%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 concise, concrete description that clearly carves out a distinctive niche and states both capability and use case. It would benefit from an explicit "Use when..." trigger clause and a few more natural synonyms.

Suggestions

Add an explicit trigger clause such as "Use when creating cinematic openings, title cards, or video chapter frames."

Include a couple of natural synonyms users might say (e.g., "intro", "title card", "movie opening") to broaden trigger coverage.

Reframe the feature list with light action verbs (e.g., "Applies film light leaks, grain, and letterbox framing...") to strengthen the specificity of capabilities.

Dimension	Reasoning	Score
Specificity	Lists several concrete visual features ("Film light leaks, grain, 16:9 letterbox, and large serif type") rather than vague abstractions, though they are noun phrases rather than explicit action verbs, leaving a minor gap.	4 / 5
Completeness	Both what (the four visual treatments) and when ("for cinematic openings or chapter cards") are stated, but the when is embedded as a prepositional phrase rather than an explicit "Use when..." trigger clause.	4 / 5
Trigger Term Quality	Natural terms a user would say ("cinematic openings", "chapter cards", "film light leaks", "letterbox") are present with good coverage, but common synonyms like "intro" or "title card" are missing.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific (film light-leak cinematic frames) with distinctive triggers ("light leaks", "letterbox", "chapter cards"), giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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: nexu-io/open-design
Path: skills/frame-light-leak-cinema/SKILL.md
Commit: d4138ea

Reviewed: 3 days 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.