video-template-frame-vignelli

Use this plugin when the user wants a "Vignelli" HyperFrames motion video — Bold typography with red accents

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/video-templates/frame-vignelli/SKILL.md

Quality

Content

72%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 exceptionally concise and well-structured as a template overview, but the workflow's final render step lacks an executable command and the process has no validation checkpoints.

Suggestions

Replace the abstract step 4 with a concrete render command or invocation example for the html-video/HyperFrames renderer so the guidance is copy-paste ready.

Add a verification checkpoint after editing (e.g. confirm animation timing and named layers are intact) and after rendering (e.g. play/inspect the MP4) to close the validation gap.

Optionally name the specific sample-copy tokens in `source/index.html` to replace, so step 2 is unambiguous without requiring a full re-read.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanation of HTML/CSS/GSAP, MP4, or headless rendering); every line earns its place with concrete specs ("9:16, default 10s, 30fps") and tight sections, matching the 'every token earns its place' anchor.	5 / 5
Actionability	Steps 1-3 give concrete, specific guidance (read `source/index.html`, replace sample copy, keep self-contained), but step 4 "Render to MP4 via the html-video / HyperFrames renderer" provides no actual command or code, leaving the key payoff step abstract; this is concrete-but-incomplete guidance with missing key details.	3 / 5
Workflow Clarity	Four steps are clearly sequenced (read → replace copy → keep self-contained → render), but there are no validation or verification checkpoints (e.g. confirm timing survived the copy swap, verify the rendered MP4 plays correctly), matching the 'steps listed but checkpoints missing' anchor.	3 / 5
Progressive Disclosure	The skill is under 50 lines and single-purpose with well-organized sections (What this template is, Best for, Workflow, Attribution); it acts as a clear overview pointing one level deep to the bundled `source/` payload, satisfying the simple-skill exception for a top score.	5 / 5
	Total	16 / 20 Passed

Description

68%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 a strong, explicit trigger clause and is highly distinctive, but it relies on a noun-phrase 'what' rather than concrete action verbs, leaving capabilities implied rather than stated.

Suggestions

Add an explicit action verb for the 'what', e.g. 'Generates a Vignelli-style HyperFrames motion video with bold typography and red accents' so capabilities are stated, not inferred.

Include a couple of natural synonyms a user might say (e.g. 'vertical promo video', 'animated bold-text card') to broaden trigger coverage.

Separate the 'what' (what it produces) and 'when' (when to use it) into distinct clauses for clearer completeness.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ("'Vignelli' HyperFrames motion video") and style descriptors ("Bold typography with red accents") but states no explicit action verb (e.g. renders/generates/creates); per the guideline to score only what is explicitly stated, actions are minimal-to-absent, though it is not pure abstract language.	2 / 5
Completeness	It has an explicit 'when' clause ("Use this plugin when the user wants...") and the em-dash clause "Bold typography with red accents" conveys the 'what' as a noun phrase; the 'what' is not stated as a separate concrete action, so it does not reach the fully-explicit anchor 5, but both what and when are present, fitting anchor 4.	4 / 5
Trigger Term Quality	The phrase "Use this plugin when the user wants a 'Vignelli' HyperFrames motion video" is a strong, natural trigger combining the named style, product, and format, plus visual descriptors ("Bold typography", "red accents"); a few natural variations (e.g. animated/promo/vertical video) are missing, so it sits above anchor 3 but below the comprehensive synonym coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Vignelli" and "HyperFrames" are highly distinctive named triggers targeting a clear niche (bold-typography red-accent motion video), with minimal risk of triggering for an unrelated skill.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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-vignelli/SKILL.md
Commit: f580271

Reviewed: about 17 hours ago

Table of Contents

Discovery Implementation Validation

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.