CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

video-template-frame-liquid-bg-hero

Use this plugin when the user wants a "Liquid Background Hero" HyperFrames motion video — WebGL-style fluid displacement background with a quote overlay, suited to video intros, landing heroes, or posters.

Quality

72%

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-liquid-bg-hero/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 clean, brief template README with a sensible four-step workflow and no padding. It is weakened by non-executable guidance — no render command, and the `source/` bundle it instructs the reader to open is missing from the skill directory — which undercuts both actionability and the disclosure structure.

Suggestions

Ship the `source/` bundle (at minimum `source/index.html`) or correct the path; the workflow's first step is unactionable without it.

Replace the vague render step with the concrete renderer invocation or command (and note how to select 16:9 / 9:16 / 1:1 and duration), which would lift actionability toward executable guidance.

Drop the intro line that duplicates the frontmatter description verbatim, and add a short post-render verification step (confirm output duration/fps or preview a frame) to give the workflow a checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanation of GSAP, WebGL, or video rendering — and the format spec ('16:9, 9:16, 1:1, default 15s, 60fps') is dense useful signal. The only trimmable token is the intro line, which repeats the frontmatter description verbatim, matching 'minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level 5.

4 / 5

Actionability

Steps are directionally concrete ('Read source/index.html', 'Replace the sample copy', 'do not introduce external network assets') but the critical render step is a pointer with no command ('Render to MP4 via the html-video / HyperFrames renderer'), and the referenced `source/index.html` bundle is absent from this skill's directory, so nothing is directly executable as written. This lands at 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable level 4.

3 / 5

Workflow Clarity

The four-step workflow (read source, swap copy, keep self-contained, render) is a clear, correctly ordered sequence with an explicit preservation constraint ('keep the motion timing and visual signature intact'). It lacks any checkpoint for verifying the render succeeded or previewing the output — minor validation gaps, since the operation is non-destructive and the feedback-loop cap does not apply.

4 / 5

Progressive Disclosure

Sections are well organized and the body is short, but the primary deep content lives in `source/index.html` ('A HyperFrames-ready HTML + CSS + GSAP motion composition, bundled under `source/`') and that directory does not exist in the skill bundle — the one reference the skill depends on is broken/unverifiable. Per the guideline to score against the actual bundle structure, this is 'some structure but references not verifiable / not clearly organized' rather than the well-signaled, resolvable references of level 4.

3 / 5

Total

14

/

20

Passed

Description

70%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 tight, well-scoped template description with an explicit use-when clause and good natural trigger terms for the video/hero context. Its main weakness is that it describes the artifact rather than the actions the skill performs (customize copy, render to MP4/WEBM at specific aspect ratios), leaving capability coverage implicit.

Suggestions

Enumerate the concrete actions the skill performs, e.g. 'Renders a WebGL-style fluid displacement hero video with quote overlay; customize the copy and export to MP4/WEBM at 16:9, 9:16, or 1:1' — this would lift specificity.

Add trigger synonyms users might naturally say — 'hero animation', 'animated/fluid background', 'video intro template' — to improve trigger-term coverage and distinctiveness against sibling templates.

Make the 'when' clause less circular by anchoring it to user intent phrases (e.g. 'Use when the user asks for a hero/intro motion video or animated landing-page background') rather than restating the template's name.

DimensionReasoningScore

Specificity

The description names the domain concretely ("HyperFrames motion video", "WebGL-style fluid displacement background with a quote overlay") but lists no actions the skill performs — what it does (render, customize, export) is only implied by naming the artifact. This matches 'names domain and 1-2 concrete actions, but not comprehensive' more than level 4, which expects several specific actions enumerated.

3 / 5

Completeness

Both parts are present: what ("WebGL-style fluid displacement background with a quote overlay") and an explicit when ("Use this plugin when the user wants a 'Liquid Background Hero' HyperFrames motion video ... video intros, landing heroes, or posters"). The 'when' clause is partly circular (use it when the user wants exactly this template) and could be more trigger-phrase driven, which is the level-4 anchor rather than the fully explicit level-5 example.

4 / 5

Trigger Term Quality

Good natural trigger coverage: "Liquid Background Hero", "motion video", "video intros", "landing heroes", "posters" are phrases a user would plausibly say. Missing common variations like "hero animation", "fluid/animated background", or "video template", so it falls just short of the comprehensive synonym coverage of level 5.

4 / 5

Distinctiveness Conflict Risk

"Liquid Background Hero" is a clear, named niche with distinct visual-signature triggers, so wrong-skill firing is unlikely. Minor overlap risk remains with sibling HyperFrames/html-video hero templates a user might request generically as a 'hero video', keeping it below level 5.

4 / 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-liquid-bg-hero/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.