video-template-frame-bold-signal

Use this plugin when the user wants a "Bold Signal Frame" HyperFrames motion video — Bold colored card on a dark gradient — big section number, nav breadcrumb, orange card sliding in, title rising.

Quality

65%

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-bold-signal/SKILL.md

Quality

Content

65%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 concise, well-structured overview with clean progressive disclosure for a small template skill. Its weaknesses are an underspecified render step (no command or pointer) and a workflow with no verification or error-recovery checkpoints.

Suggestions

Make the render step executable: give the exact command or entry point for the html-video/HyperFrames renderer (e.g., a script invocation or the renderer invocation with output flags for MP4/WEBM and aspect ratio), rather than the vague "Render to MP4 via the html-video / HyperFrames renderer".

Add a verification checkpoint after the render step (e.g., confirm the output file exists and duration/aspect ratio match the requested format) so the workflow has an explicit feedback loop.

Remove the first body paragraph that duplicates the frontmatter description verbatim, or replace it with new information (e.g., the named GSAP layers or timeline highlights) to make every token earn its place.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids concept explanations; the only padding is the first paragraph repeating the frontmatter description verbatim ("Bold colored card on a dark gradient — big section number, nav breadcrumb, orange card sliding in, title rising."), which keeps it off anchor 5.	4 / 5
Actionability	Steps 1–3 are concrete (read `source/index.html`, replace sample copy, keep assets self-contained), but step 4 "Render to MP4 via the html-video / HyperFrames renderer" provides no command, script path, or link — key execution details are missing, matching anchor 3 rather than 4.	3 / 5
Workflow Clarity	A clear four-step sequence exists, but there are no validation checkpoints (no step to verify the render or check output) and no error-recovery guidance, which fits anchor 3 ("checkpoints missing or implicit") rather than 4 ("most checkpoints present").	3 / 5
Progressive Disclosure	The skill is under 50 lines, well-organized into clear sections, and points to a single one-level-deep reference (`source/index.html`) that is clearly signaled in the workflow — meeting anchor 5 under the simple-skill exception.	5 / 5
	Total	15 / 20 Passed

Description

66%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 distinctive and explicitly triggers via a 'Use when' clause, but its trigger is narrow and circular (only matching the exact template name), and it describes visual appearance rather than concrete capabilities. Keyword coverage lacks common synonyms a user would naturally say.

Suggestions

Broaden trigger terms beyond the exact template name: add natural phrases like 'section divider', 'chapter intro', 'title card', or 'bold animated opener' so users who don't know the template name can still invoke it.

State the concrete capability (e.g., 'Renders a bold section-divider motion video... to MP4/WEBM at 16:9, 9:16, 1:1') instead of only describing the visual look, which would also raise specificity.

Avoid describing the 'what' purely through visual elements; pair the appearance description with what the skill actually does (create, customize, and render the video).

Dimension	Reasoning	Score
Specificity	Names the domain ("HyperFrames motion video") and concrete visual components ("big section number, nav breadcrumb, orange card sliding in, title rising"), but these describe appearance rather than several executable actions, matching anchor 3 rather than 4's broader action coverage.	3 / 5
Completeness	Both 'what' (the described visual composition) and 'when' ("Use this plugin when the user wants a 'Bold Signal Frame' HyperFrames motion video") are present, but the trigger is circular — it fires only when the user already names the exact template — so it falls short of anchor 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant keywords ("motion video", "HyperFrames", "section number", "title") but misses natural user variations such as "intro", "section divider", "animation", or "title card", fitting anchor 3 (relevant keywords present, common synonyms missing).	3 / 5
Distinctiveness Conflict Risk	"Bold Signal Frame" + "HyperFrames" is a clearly named niche with distinct triggers and minimal overlap risk against generic video or slide skills.	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-bold-signal/SKILL.md
Commit: 1b47e60

Reviewed: 3 days 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.