CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

video-template-frame-light-leak-cinema

Use this plugin when the user wants a "Light-Leak Cinematic Frame" HyperFrames motion video — Film light leaks, grain, 16:9 letterbox, and large serif type for cinematic openings or chapter cards.

Quality

71%

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 ./plugins/_official/video-templates/frame-light-leak-cinema/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 short, well-structured template skill that defers detail to its bundle appropriately and wastes almost no tokens. Its weaknesses are executional: the render step is named but never shown as a runnable command, and the workflow ends without any verification that the render succeeded or that the user's copy fits the timeline.

Suggestions

Replace step 4's vague "Render to MP4 via the html-video / HyperFrames renderer" with the actual command or invocation, so the workflow is executable end-to-end without guessing.

Add a validation checkpoint after content replacement (e.g. confirm headline/label lengths fit the existing animation timing before rendering) and a verify step after rendering (e.g. check output duration, fps, and aspect ratio).

Drop the sentence under the H1 that repeats the frontmatter description verbatim; the body gains nothing from it.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but the line under the H1 ("Film light leaks, grain, 16:9 letterbox, and large serif type for cinematic openings or chapter cards.") duplicates the frontmatter description verbatim and could be trimmed. Efficient overall, just above the midpoint — not 5 because of that removable redundancy.

4 / 5

Actionability

Steps 1–3 are concrete ("Read `source/index.html`", "Replace the sample copy", "do not introduce external network assets"), but step 4 "Render to MP4 via the html-video / HyperFrames renderer" provides no command or invocation and no pointer to how the renderer is called. Matches the anchor for concrete-but-incomplete guidance with missing key details.

3 / 5

Workflow Clarity

A clear four-step sequence is present, but there are no validation checkpoints anywhere — no preview step, no verify-render step, and no check that replacement copy fits the existing motion timing. This is a multi-step workflow, so the simple-skill exception does not apply; it sits at anchor 3 (sequence present, checkpoints missing) rather than 4 (most checkpoints present).

3 / 5

Progressive Disclosure

Under 50 lines, single-purpose, cleanly sectioned (What this template is / Workflow / Attribution), with all detail correctly deferred to the `source/` bundle referenced one level deep (`source/index.html`). Matches the well-organized simple-skill ideal with no inlined content that belongs elsewhere.

5 / 5

Total

15

/

20

Passed

Description

66%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 distinctive, clearly-triggered description that names its niche precisely, but it describes what the output looks like rather than what the skill does, and it lacks common synonym phrasing. Adding one action verb and a few natural user phrases would lift it substantially.

Suggestions

State the action explicitly, e.g. "Renders a Light-Leak Cinematic Frame HyperFrames motion video with film light leaks, grain, 16:9 letterbox, and large serif type" — this moves specificity and completeness toward the top anchors.

Add natural trigger synonyms users would actually say: "cinematic intro", "film burn", "movie title card", or "title sequence", not just "cinematic openings or chapter cards".

Include the deliverable formats in the description (MP4/WEBM) so the what-side answers what the user receives, not only what the video contains.

DimensionReasoningScore

Specificity

Names the domain (HyperFrames motion video) and lists four concrete visual elements ("Film light leaks, grain, 16:9 letterbox, and large serif type"), but states no actions — no create/render/customize verbs appear, so it describes attributes rather than capabilities.

3 / 5

Completeness

The "when" is explicit ("Use this plugin when the user wants..."), and the "what" is present via the enumerated visual elements, but the actual action (creating/rendering the video) is only implied rather than stated. Not 5 because anchor 5 requires both what and when fully explicit with concrete trigger phrasing.

4 / 5

Trigger Term Quality

Includes some natural phrases users would say ("cinematic openings", "chapter cards", "light leak"), but misses common synonyms and variations such as "cinematic intro", "film burn", "movie title card", or "title sequence".

3 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche ("Light-Leak Cinematic Frame" HyperFrames video) with distinctive trigger terms; minimal risk of firing for the wrong skill.

5 / 5

Total

15

/

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

nexu-io/open-design

Path

plugins/_official/video-templates/frame-light-leak-cinema/SKILL.md

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.