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.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is a well-structured, action-dense workflow with explicit validation checkpoints and feedback loops, and excellent progressive disclosure via a reference-routing table backed by real bundle files. The two minor gaps are some restated routing guidance and the absence of a full index.html code template in Step 3.

Suggestions

Add a minimal copy-paste index.html skeleton in Step 3 showing the #stage div, one scene div, and the paused gsap.timeline registration, so the emit step is fully executable rather than prose-described.

De-duplicate the front-door routing guidance (currently repeated in the update note, overview, and 'When to use') into a single canonical block to trim tokens.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no explaining what Remotion/GSAP/SSIM are), with commands and a mapping table earning their tokens; the only drag is that the routing/trigger guidance is restated across the top update note, the overview, and the 'When to use' section, which could be tightened.

4 / 5

Actionability

Step 1's lint, Step 2's source→reference table, and Step 4's copy-paste bash commands are concrete and executable, but Step 3 describes the index.html structure in prose rather than providing a full copy-paste template, leaving a minor gap.

4 / 5

Workflow Clarity

Five explicitly sequenced steps with validation checkpoints: Step 1 lint fires a blocker → stop + read escape-hatch, and Step 4 SSIM diff failure → frame_strip.sh → re-read reference form a clear validate→fix→retry feedback loop.

5 / 5

Progressive Disclosure

SKILL.md is a clean overview with a well-signaled source-pattern→reference-file table; all 11 referenced reference files, the three scripts, and the test-corpus runner exist, and references stay one level deep with markdown links for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

82%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 strong: it explicitly answers both what and when, provides natural trigger synonyms, and sharply scopes its niche with negative triggers and escape routes. The only gap is that it names essentially one capability (porting) rather than multiple distinct actions, which limits specificity.

Suggestions

Consider naming the concrete deliverables the port produces (e.g., 'emits index.html with a paused GSAP timeline and TRANSLATION_NOTES.md') to lift specificity beyond a single action.

Optionally add a composition-file trigger (e.g., 'a Remotion <Composition> / src/Composition.tsx') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (Remotion → HyperFrames) and one concrete action ('Port an existing Remotion (React) composition's source to HyperFrames HTML'), but the port/convert/migrate/translate verbs all describe the same single action rather than multiple distinct capabilities, so it does not reach the 'several specific actions' bar.

3 / 5

Completeness

Explicitly states what it does (port Remotion source to HyperFrames HTML) and when to use it ('Use ONLY on an explicit ask to port/convert/migrate/translate'), with concrete trigger phrases plus negative triggers ('passing Remotion mention, reference-only code') and an escape route ('Unclear → /hyperframes').

5 / 5

Trigger Term Quality

Includes natural user phrasings ('port/convert/migrate/translate a Remotion source') with good synonym coverage, but lacks file-extension-style triggers and a few common variations, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear one-way Remotion→HyperFrames niche with explicit routing away from /general-video and /hyperframes for non-matching cases, giving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.