CtrlK
BlogDocsLog inGet started
Tessl Logo

video-template-frame-data-chart-nyt

Use this plugin when the user wants a "NYT-Style Data Chart Frame" HyperFrames motion video — NYT-newsroom typography, staggered reveal animation, and editorial-grade charts (line, bar, or range band).

56

Quality

65%

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-chart-nyt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a tight, well-organized overview with a sensible workflow, but its terminal render step is not executable — it names the renderer without a command — and the bundle it depends on is unverifiable in the delivered skill. Adding a concrete render invocation would close the largest gap.

Suggestions

Replace the vague render step with an executable command or minimal CLI example (e.g., the exact html-video/HyperFrames render invocation with output path and aspect-ratio flags).

Add a brief post-render validation checkpoint (verify duration, aspect ratio, and that no network assets broke the headless render).

Remove the line that repeats the frontmatter description verbatim, and include a short file listing of `source/` so the referenced bundle structure is navigable.

DimensionReasoningScore

Conciseness

Genuinely lean: concrete render specs ("MP4 / WEBM at 16:9, 9:16, 1:1, default 15s, 60fps") with no explanation of concepts Claude already knows. Not a 5 because the opening line duplicates the frontmatter description verbatim — one line that does not earn its place.

4 / 5

Actionability

Step 1 points to a concrete path (`source/index.html`) and steps 2-3 are specific, but the terminal and most critical step ("Render to MP4 via the html-video / HyperFrames renderer") provides no executable command, and there is no code or CLI example anywhere in the body. Concrete guidance exists but is incomplete.

3 / 5

Workflow Clarity

A clear four-step sequence (read template → replace copy → keep self-contained → render) with a checkpoint-like constraint ("do not introduce external network assets that would break a headless render"). Not a 5 because there is no validation step for the render output, and this is a multi-step process so the simple-skill exception does not fully apply.

4 / 5

Progressive Disclosure

A short, well-sectioned overview with a clearly signaled one-level-deep reference (`source/index.html`). Not a 5 because, scored against the actual bundle structure, no bundle files exist in this skill copy — the referenced path cannot be verified and no listing of the `source/` tree is provided to aid navigation.

4 / 5

Total

15

/

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 has an explicit and well-formed trigger clause and a distinctive niche framing, but it describes the template's visual attributes rather than the concrete actions the skill performs, and its natural-language trigger coverage is moderate. It reads as product-copy for a known template rather than a capability statement.

Suggestions

State the action the skill performs, not just the artifact's look — e.g., "Builds a NYT-style data chart motion video from a bundled HTML/CSS/GSAP template, rendering to MP4/WEBM at 16:9, 9:16, or 1:1."

Broaden trigger terms with natural user phrasings and synonyms: "data visualization video", "animated chart", "editorial infographic", "newsroom-style chart".

Keep "HyperFrames" but pair it with a generic term ("motion/video composition") so users who don't know the product name still match the trigger.

DimensionReasoningScore

Specificity

Names the domain concretely ("NYT-Style Data Chart Frame", "editorial-grade charts (line, bar, or range band)") but lists attributes rather than actions — it never states what the skill does (e.g., create or render a video from a template). This matches the anchor for naming the domain with only 1-2 concrete elements, not the several-specific-actions anchor above.

3 / 5

Completeness

Both parts are explicit: "Use this plugin when the user wants a..." is a clear when-clause, and the what is conveyed via typography/animation/chart-type attributes. Not a 5 because the "what" describes the artifact's look rather than the skill's actions, so it is less concrete than the anchor-5 example.

4 / 5

Trigger Term Quality

Contains relevant natural phrases ("NYT-Style", "data chart", "motion video", chart type names) but misses common variations like "data visualization video", "animated chart", or "editorial infographic", and leans on product jargon ("HyperFrames"). Some relevant keywords, but coverage of natural user phrasings is incomplete.

3 / 5

Distinctiveness Conflict Risk

The "NYT-Style... HyperFrames motion video" framing is a clear niche with distinct triggers; only the generic "charts (line, bar...)" terms risk minor overlap with general dataviz skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than the minimal-conflict anchor 5.

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.

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