CtrlK
BlogDocsLog inGet started
Tessl Logo

video-template-frame-play-mode

Use this plugin when the user wants a "Play Mode" HyperFrames motion video — Playful elastic animations

53

Quality

60%

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-play-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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.

The body is lean and well-structured for a simple template skill, but it lacks executable render commands and any validation step for the output render. Progressive disclosure is adequate for the short body yet offers no deeper references despite pointing at a source/ bundle.

Suggestions

Add the concrete render command (e.g., the exact html-video/HyperFrames renderer invocation) so the workflow is copy-paste executable.

Insert a validation/verification checkpoint after the render step (e.g., confirm MP4 output, 16:9 aspect, 10s duration) to satisfy the batch-output feedback-loop requirement.

Signpost one-level-deep references for the source/ bundle (e.g., a brief note on what source/index.html's named layers are, or a link to a layers reference) so deeper detail is navigable.

DimensionReasoningScore

Conciseness

The body is short and assumes competence — it states render specs (16:9, 10s, 30fps) and a 4-step workflow without padding or explaining what HTML/GSAP are — with only minor instances that could be trimmed.

4 / 5

Actionability

Steps reference a real file ('Read source/index.html') and give a render path, but contain no executable commands or code samples for the actual edit/render cycle, leaving the operator without copy-paste-ready instruction.

3 / 5

Workflow Clarity

A 4-step sequence is listed, but there is no validation/verification checkpoint (e.g., confirm the render, check output format) before the final render — and rendering a video is a batch/output operation, so the missing feedback loop caps this at 3 per the rubric.

3 / 5

Progressive Disclosure

Structure is reasonable (What/Workflow/Attribution) and content is appropriately short, but there are no one-level-deep reference files signposted for detail (no references/ scripts/ assets/ exist), and the bundle's own source/ tree is referenced but not navigated.

3 / 5

Total

13

/

20

Passed

Description

62%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.

The description establishes a clear, distinct trigger ('Play Mode' HyperFrames motion video) with explicit use-when guidance, but it is light on enumerated capabilities and natural trigger synonyms. It is concise and free of fluff but reads more as a tagline than a capability list.

Suggestions

Add 2-3 concrete capability phrases (e.g., 'renders HTML+CSS+GSAP to MP4/WEBM at 16:9') so specificity reaches comprehensive coverage.

Broaden trigger terms with user-natural synonyms like 'animated social ad', 'bounce/elastic animation', or 'motion graphics video'.

Use third-person capability voice (e.g., 'Renders a playful elastic motion video...') rather than the second-person 'Use this plugin when the user wants' phrasing.

DimensionReasoningScore

Specificity

Names the domain (HyperFrames motion video, "Play Mode") and implies the concrete action of producing a playful elastic-animation video, but lists no enumerated capabilities — matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Has a clear 'when' via 'Use this plugin when the user wants...' and a clear 'what' via 'Play Mode HyperFrames motion video — Playful elastic animations', but the trigger could be more specific (no mention of social ads or format).

4 / 5

Trigger Term Quality

Includes the natural phrase 'Play Mode' and 'motion video', but lacks common synonyms users would say (e.g., 'animated video', 'bounce animation', 'elastic motion') — fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The 'Play Mode' + 'HyperFrames motion video' niche is fairly distinct from generic video skills with only minor overlap risk against other motion-video templates.

4 / 5

Total

14

/

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.

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
nexu-io/open-design
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.