CtrlK
BlogDocsLog inGet started
Tessl Logo

video-template-frame-data-rollup

Use this plugin when the user wants a "Data Rollup Frame" HyperFrames motion video — A native Remotion data frame — bars grow from zero by real data via spring physics while the figures roll 0→target in sync.

57

Quality

66%

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-data-rollup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 exemplary in its conciseness and assumes Claude's intelligence, but it stops short of executable guidance: no concrete render command or code snippet, and no verification step for the rendered output. A referenced source/ bundle is also absent from the disk.

Suggestions

Add the concrete render command (e.g., the exact HyperFrames/renderer invocation) so the final step is copy-paste executable rather than directional.

Insert an explicit validation/verify checkpoint after rendering (e.g., confirm the MP4 exists, plays at 30fps, and the roll-up completes before the 15s end) to lift workflow clarity.

Either ship the referenced source/ bundle (with source/entry.ts) or remove/qualify the source/ reference so navigation does not point at missing files.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and assumes Claude's competence; it never explains concepts Claude already knows and every line carries information.

5 / 5

Actionability

Gives concrete directional guidance ('Read source/entry.ts', 'Replace the sample copy', 'Render to MP4 via the html-video / HyperFrames renderer') but provides no copy-paste code or exact render command, leaving key execution details unspecified.

3 / 5

Workflow Clarity

A clear 4-step numbered sequence is present, but there is no validation/verify checkpoint for the render output, so checkpoints are missing rather than merely implicit.

3 / 5

Progressive Disclosure

Sections are well-organized and the body is an overview rather than a wall of text, but it references a source/ bundle (source/entry.ts, source/) that is not present on disk, a minor navigation defect that keeps it below the clean simple-skill 5.

4 / 5

Total

15

/

20

Passed

Description

63%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 is specific to a distinct niche and answers both what and when, but its trigger terms lean heavily on product-internal jargon rather than natural user language, weakening discoverability. Rewording triggers around what a user would actually say would lift completeness and trigger quality.

Suggestions

Add natural user-facing trigger phrases (e.g., 'animated bar chart video', 'count-up / rolling numbers video', 'weekly metrics growth bars') alongside the product term 'Data Rollup Frame'.

Include common synonyms and the file/format angle if applicable (e.g., MP4/WEBM motion graphic) to broaden natural keyword coverage.

Keep the concrete action list but phrase the 'when' clause in terms a user would say ('Use when the user wants an animated data bar/count-up video'), not just the internal template name.

DimensionReasoningScore

Specificity

Names the domain and concrete technical actions ('bars grow from zero by real data via spring physics while the figures roll 0→target in sync'), but stops short of a comprehensive multi-action list like the 5 anchor.

4 / 5

Completeness

Both 'what' ('A native Remotion data frame — bars grow from zero...') and 'when' ('Use this plugin when the user wants a Data Rollup Frame HyperFrames motion video') are present, but the 'when' is tied to product jargon rather than explicit user trigger phrases.

4 / 5

Trigger Term Quality

Terms like 'HyperFrames motion video', 'spring physics', and 'Data Rollup Frame' are product-specific jargon rather than phrases a user would naturally say; common synonyms (e.g., animated bar chart, count-up) are absent.

2 / 5

Distinctiveness Conflict Risk

Targets a clear niche (HyperFrames data-rollup motion video) with distinct triggers and minimal overlap risk with other skills.

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.

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.