CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-to-hyperframes

Port an existing Remotion (React) composition's source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

75

Quality

94%

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

SKILL.md
Quality
Evals
Security

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.

An exemplary skill body: a gated 5-step workflow with quantified validation and error-recovery loops, fully executable commands, precise output-format specs, and textbook progressive disclosure via an API-map index. The only weaknesses are mild redundancy in the three separate scope/boundary sections and a date-stamped baseline table that will age.

Suggestions

Consolidate the scope guidance: the front-door blockquote, 'When to use', and 'What this skill explicitly does NOT do' repeat the same boundaries; merge the latter two and drop the trigger-phrase list that duplicates the frontmatter description.

Show the exact lint invocation in Step 1 (e.g. `python scripts/lint_source.py <src-dir>`) the way Steps 2 and 4 show theirs, so every step's first command is copy-paste ready.

Move the date-stamped validated-baseline table into references/eval.md next to the thresholds it documents, keeping the body's SSIM guidance to the rule rather than the snapshot numbers.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no concept explanations, no library tutorials — and every workflow step carries a command, rule, or spec. Minor trimming is possible: scope boundaries are stated three times (front-door blockquote, "When to use", "What this skill explicitly does NOT do"), largely restating the frontmatter, and the date-stamped validated-baseline table ("as of 2026-04-27") is time-sensitive detail. Anchor 4 ('efficient; minor instances that could be trimmed') fits; anchor 3's 'unnecessary explanation' is too harsh since nothing teaches known concepts.

4 / 5

Actionability

Fully executable guidance throughout: lint via scripts/lint_source.py with named blockers/warnings/info, catalog search with the exact `npx hyperframes catalog --query ... --json` invocation, a precise Step-3 output spec (data attributes, paused gsap.timeline, window.__timelines registration), and copy-paste render/diff commands (`npx remotion render <CompositionId> out/baseline.mp4`, `npx hyperframes render --skill=... --output ...`, render_diff.sh) with the pixel-format fix (Config.setVideoImageFormat("png") + Config.setColorSpace("bt709")). Matches anchor 5; the only soft spot is that the lint script's exact CLI arguments are implied rather than shown.

5 / 5

Workflow Clarity

A clear 5-step sequence (lint → plan → generate → validate → document) with explicit checkpoints and feedback loops: blockers stop translation and route to escape-hatch.md; a failed SSIM diff triggers frame_strip.sh to localize diverging frames before re-reading the relevant reference; thresholds are quantified per tier. This matches anchor 5 (explicit validation steps with error-recovery loops); the batch/destructive cap at 3 does not apply because validation is central.

5 / 5

Progressive Disclosure

Model progressive disclosure: the SKILL.md is an overview; api-map.md is an index with a source-construct → reference table covering all 11 reference files (all verified present in the bundle), scripts and assets are referenced by path and exist, and it explicitly instructs "Don't load all of them — load only what the specific source needs." References are one level deep. One minor blemish: the conditional link to ../hyperframes/references/plugin-installation.md does not resolve in this standalone checkout, but it is explicitly scoped to plugin installs, so navigation within the bundle remains clear.

5 / 5

Total

19

/

20

Passed

Description

95%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 crisp, well-bounded description: one concrete capability, explicit trigger phrases with synonyms, explicit exclusions, and routing for ambiguous cases. Voice is imperative (matching the good examples), not first/second person, so no penalty applies.

DimensionReasoningScore

Specificity

"Port an existing Remotion (React) composition's source to HyperFrames HTML" names the domain and a fully concrete action with explicit one-way scope ("one-way, Remotion-only"), and it also concretely routes the negative cases ("is a fresh build (/general-video)", "Unclear → /hyperframes"). It sits between anchor 3 and 5: more than 1-2 vague actions, but the verbs port/convert/migrate/translate are synonyms of a single capability rather than several distinct listed actions, so 4 fits best.

4 / 5

Completeness

Explicitly answers what ("Port an existing Remotion (React) composition's source to HyperFrames HTML") and when ("Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source") with concrete trigger phrasing, plus explicit exclusions. This matches anchor 5 exactly; anchor 4's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms users would actually say: "port/convert/migrate/translate a Remotion source", plus a quoted natural user phrase ("make something like my Remotion video") and both tool names. Anchor 5's synonym-level coverage is met; the domain has no meaningful file extension to include.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Remotion → HyperFrames one-way port) with explicit negative space — a passing Remotion mention or reference-only code routes elsewhere, fresh builds go to /general-video, uncertainty goes to /hyperframes. Minimal conflict risk with any other skill, matching anchor 5.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
heygen-com/hyperframes
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.