hyperframes

Render MP4/WebM videos from HTML compositions.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/creative/hyperframes/SKILL.md

Quality

Content

92%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 strong, executable reference: concrete commands throughout, an explicitly sequenced workflow with validation checkpoints and feedback loops, and clean progressive disclosure to verified reference files. The only nit is minor repetition of the preview-cleanup warning.

Suggestions

Collapse the preview/swiftshader-CPU warning to a single canonical spot (e.g. Cleanup) and reference it from Quick Reference and Pitfalls to trim repeated tokens.

Tighten a few long sentences in the Audio-reactive and Pitfalls bullets to recover additional token budget.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence with executable commands throughout, but the preview/swiftshader-CPU warning is restated in three places (Quick Reference, Cleanup, Pitfalls) and a few sentences run long, keeping it just short of fully lean.	4 / 5
Actionability	It provides copy-paste-ready, executable commands and code (init, lint, validate, inspect, render flags, TTS, transcribe, pkill cleanup) with specific examples covering the common cases end to end.	5 / 5
Workflow Clarity	The 8-step Procedure is clearly sequenced with explicit validation checkpoints (lint/validate/inspect, animation-map flags to "fix or justify each") and an error-recovery feedback loop (render fails -> hyperframes doctor).	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled, one-level-deep references to real bundle files (composition.md, cli.md, gsap.md, features.md, website-to-video.md, troubleshooting.md) plus an organized References section; navigation is easy and nothing is nested.	5 / 5
	Total	19 / 20 Passed

Description

53%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 concise and third-person with a clear capability statement, but it omits any "when to use" trigger guidance and uses only moderately natural keywords. Adding a "Use when..." clause with user-facing terms (video, animation, motion graphics) would raise completeness and trigger quality.

Suggestions

Append a "Use when..." clause naming concrete triggers (e.g. "Use when the user asks to render a video from HTML, a script, or a website, or wants animated titles, captions, or motion graphics.").

Add natural-language synonyms users actually say ("video", "animation", "motion graphics", "HTML to video") alongside MP4/WebM to improve trigger-term coverage.

Mention one more concrete capability (e.g. captions/TTS or scene transitions) to broaden specificity beyond a single render action.

Dimension	Reasoning	Score
Specificity	"Render MP4/WebM videos from HTML compositions" names the domain (HTML compositions) and one concrete action (render to MP4/WebM) but lists no additional actions, matching the 1-2-concrete-actions anchor.	3 / 5
Completeness	It gives a clear "what" (render MP4/WebM from HTML compositions) but no "when"/"Use when..." clause; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant terms ("MP4/WebM videos", "HTML compositions") but omits the natural phrases users would say ("animation", "make a video", "motion graphics"), so keyword coverage has gaps.	3 / 5
Distinctiveness Conflict Risk	The HTML-to-video niche is mostly distinct from other skills; the only minor overlap risk is with sibling video skills (manim-video, meme-generation), and the absence of explicit triggers slightly raises ambiguity versus those.	4 / 5
	Total	13 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/creative/hyperframes/SKILL.md
Commit: 6680afb

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