video-template-frame-decision-tree

Use this plugin when the user wants a "Decision Tree" HyperFrames motion video — Animated flowchart with branching paths

Quality

72%

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-decision-tree/SKILL.md

Quality

Content

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

A lean, well-structured template README whose workflow is easy to follow, undermined by two concrete gaps: the referenced `source/index.html` bundle is absent, and the render step provides no executable command. Fixing the dangling reference and specifying the renderer invocation would lift actionability and navigation substantially.

Suggestions

Ship the `source/` bundle (or correct the path) so the workflow's step 1 — 'Read `source/index.html` to understand the named layers and the animation timeline' — points to a file that actually exists.

Replace 'Render to MP4 via the html-video / HyperFrames renderer' with the actual renderer command or a copy-paste-ready invocation, so the final step is executable rather than descriptive.

Add a brief verification step after rendering (e.g., check output duration/resolution matches 15s at 16:9 30fps) to close the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is roughly 30 lines with zero padding: no explanation of what GSAP, HTML, or rendering are, no filler, and every section (what/template is, best-for, workflow, attribution) earns its place — matching the 'lean and efficient; assumes Claude's competence' anchor.	5 / 5
Actionability	Steps are directionally concrete ('Replace the sample copy (headlines, figures, labels) with the user's real content; keep the motion timing and visual signature intact'), but there are no executable commands — 'Render to MP4 via the html-video / HyperFrames renderer' gives no invocation — and the referenced 'source/index.html' does not exist in the skill's bundle, leaving key execution details missing.	3 / 5
Workflow Clarity	The four steps form a clear, sensibly ordered sequence (understand → replace copy → keep self-contained → render) with per-step constraints, matching 'clear sequence with most checkpoints present; minor validation gaps'. It is not 5 because the render step lacks any how-to and there is no output verification step.	4 / 5
Progressive Disclosure	Sections are well organized and the pointer to the template ('bundled under `source/`', 'Read `source/index.html`') is one level deep and clearly signaled. However, no `source/` directory (nor references/, scripts/, assets/) actually ships with the skill, so the sole external reference is dangling and navigation fails — better than minimal structure, but below the 'well-signaled references, easy navigation' bar.	3 / 5
	Total	15 / 20 Passed

Description

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

A concise, well-triggered description for a narrowly scoped template skill. The 'when' is explicit and the niche is unmistakable; the main weakness is that the 'what' is a single descriptive tagline with no enumerated actions or capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain concretely ('"Decision Tree" HyperFrames motion video') and characterizes the deliverable ('Animated flowchart with branching paths'), but lists no actions — it describes the artifact rather than what the skill does, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the multiple-action coverage of 4.	3 / 5
Completeness	Both parts are explicitly present: the 'when' via 'Use this plugin when the user wants a "Decision Tree" HyperFrames motion video' and the 'what' via 'Animated flowchart with branching paths'. It falls short of 5 because the 'what' is a thin tagline rather than concrete trigger phrases describing capabilities.	4 / 5
Trigger Term Quality	Terms like 'Decision Tree', 'motion video', 'flowchart', and 'branching paths' are natural phrases a user wanting this template would say, but common variations (e.g., 'animated diagram', 'process flow video', 'flowchart animation') are missing, so keyword coverage is good but not comprehensive.	4 / 5
Distinctiveness Conflict Risk	The trigger is a clear niche — a specific HyperFrames decision-tree video template — with distinct terms ('HyperFrames', 'motion video', 'Decision Tree') that would not naturally invoke any other skill, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 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-decision-tree/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.