CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-to-hyperframes

Bring existing video code or footage into HyperFrames and verify it frame by frame against the original - Remotion first, also Motion Canvas, Lottie, Three.js, p5.js, canvas or plain HTML/CSS animation, or renders from Manim, After Effects or Blender. Use to port, convert, migrate or reuse work made with another tool.

Quality

95%

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

96%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 operational skill body: lean, command-dense, with a validated multi-step workflow and clean one-level reference routing. The single structural defect is a missing referenced file (references/mixing.md) that leaves two pointers dangling.

Suggestions

Create references/mixing.md (or remove the "form in /media-use → references/mixing.md" pointers from media.md and limitations.md) so no reference in the bundle dangles.

Consider briefly mentioning the shipped test corpus (assets/test-corpus) in the body's verify step so its existence is discoverable without opening references/eval.md.

DimensionReasoningScore

Conciseness

The ~46-line body is dense and operational throughout: a levels table, a five-step Native workflow, a routing table to reference files, and concrete gotchas ("without it every bordered or padded element grows by its border and padding", "or the diff measures the encoders (about 0.05 SSIM)"). Every token carries non-obvious porting knowledge and nothing explains concepts Claude already knows.

5 / 5

Actionability

Commands are copy-paste ready with real flags and arguments: `python3 <SKILL_DIR>/scripts/lint_source.py <source dir>`, `npx hyperframes diff <original.mp4> . --at <t,…>`, `npx hyperframes catalog --query "…" --json`, `Config.setVideoImageFormat("png")`, and a concrete `<video class="clip" data-has-audio="true" src="assets/x.mp4">` snippet. Blockers are enumerated by exact name (useState, MUI, Chakra, delayRender) rather than described abstractly.

5 / 5

Workflow Clarity

The Native path is a numbered sequence (lint → translate → keep editable → diff at sample times → full rendered diff → write TRANSLATION_NOTES.md) with explicit validation at each stage, blocker-handling guidance ("don't translate: host them or refactor them out, never approximate"), tiered diff thresholds deferred to references/eval.md, and a final-message checklist. The three-level decision table routes every source type to a well-defined path.

5 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled routing table mapping each Remotion API to a one-level-deep reference file, all of which exist in the bundle. However, `media.md` and `limitations.md` both point to `references/mixing.md`, which is absent from the bundle — a dangling second-level reference that breaks navigation, a minor organization gap against the top anchor.

4 / 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 tightly written description that names a clear niche, comprehensive source-tool triggers, and an explicit use clause. The only softness is that the distinct concrete actions boil down to import-and-verify, with the remaining verbs acting as synonyms.

DimensionReasoningScore

Specificity

Concrete actions are stated — "Bring existing video code or footage into HyperFrames and verify it frame by frame against the original" plus "port, convert, migrate or reuse" — and coverage of source tools (Remotion, Motion Canvas, Lottie, Three.js, p5.js, Manim, After Effects, Blender) is comprehensive. The distinct actions reduce to roughly two (import, verify) with the rest being synonyms, a minor gap versus the comprehensive-actions anchor.

4 / 5

Completeness

The "what" is explicit ("Bring existing video code or footage into HyperFrames and verify it frame by frame against the original") and the "when" is given as equivalent explicit trigger guidance ("Use to port, convert, migrate or reuse work made with another tool") anchored by concrete tool names. Both halves are answered with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Names the exact tools a user would mention ("Remotion", "Lottie", "Three.js", "Manim", "After Effects", "Blender") alongside natural verb synonyms ("port, convert, migrate or reuse") and "video code or footage". Coverage of natural trigger phrases, including framework names and render-tool names, is comprehensive.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — importing into HyperFrames from named external tools — and its triggers (specific tool names plus port/convert/migrate verbs) are unlikely to fire for an unrelated skill. Conflict risk with other skills is minimal.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

heygen-com/hyperframes

Path

skills/remotion-to-hyperframes/SKILL.md

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.