CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-to-hyperframes

Port an existing Remotion (React) composition to HyperFrames HTML. Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source. Do NOT use: (a) authoring a new HyperFrames composition; (b) Remotion mentioned in passing; (c) Remotion code shared as reference only; (d) "same video as my Remotion one" without explicit migrate request — treat as fresh build. Doubt → `/general-video`. One-way, Remotion-only: no reverse export (HyperFrames→Remotion or any framework), no non-Remotion source (After Effects, Framer Motion, plain React/CSS) → out of scope, re-create via `/general-video`. Flags unsupported patterns (useState, useEffect, async calculateMetadata, third-party React libs, `@remotion/lambda`) and recommends runtime interop over lossy translation. Unsure whether to port vs. build fresh, or only a passing Remotion mention? → /hyperframes.

75

Quality

92%

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%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable porting workflow with strong progressive disclosure and a genuine validate→fix feedback loop. The only weakness is moderate redundancy in restating the skill's scope exclusions across multiple sections, which slightly dilutes token efficiency.

Suggestions

Collapse the repeated scope-exclusion messaging: state the one-way / Remotion-only / non-Remotion-source exclusions once (e.g. in 'When to use') and have the closing 'What this skill explicitly does NOT do' section reference it rather than re-explain, since the description already covers the same ground.

Trim the opening blockquote, which restates trigger guidance already present in the description and the 'When to use' section; a one-line pointer would preserve the route-confirmation cue at lower token cost.

DimensionReasoningScore

Conciseness

The body is mostly lean and actionable, but the scope-exclusion messaging (one-way Remotion-only, Do-NOT-use, NOT SUPPORTED) is restated across the opening blockquote, 'When to use', and 'What this skill explicitly does NOT do' — and largely duplicates the description — so it could be tightened. Not a level 3 because the redundancy is noticeable; not a level 1 because it never explains concepts Claude already knows.

2 / 3

Actionability

Provides fully executable commands (`npx remotion render <CompositionId> out/baseline.mp4`, `npx hyperframes render --skill=remotion-to-hyperframes --output ../hf.mp4`, `scripts/render_diff.sh ...`), a concrete emit spec for `index.html` with named `data-*` attributes, and copy-paste config (`Config.setVideoImageFormat("png")` + `Config.setColorSpace("bt709")`).

3 / 3

Workflow Clarity

A clear five-step sequence (Lint→Plan→Generate→Validate→Document) with a hard stop-condition in Step 1 ('If any blocker fires, stop') and an explicit validate→diagnose→retry loop in Step 4 ('If the diff fails, run frame_strip.sh ... then re-read the relevant reference').

3 / 3

Progressive Disclosure

SKILL.md is an overview that delegates detail to one-level-deep references via a 'Source contains → Load reference' table; all 11 referenced markdown files, the 3 scripts, and assets/test-corpus/run.sh exist on disk, and the full API map is offloaded to references/api-map.md rather than inlined.

3 / 3

Total

11

/

12

Passed

Description

100%

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 scoped, highly specific description that crisply states the one action it performs and the exact conditions under which to invoke it, while actively disambiguating from neighboring skills. It is a strong example of a trigger-rich, low-conflict description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Port an existing Remotion (React) composition to HyperFrames HTML', 'Flags unsupported patterns (useState, useEffect, async calculateMetadata...)', 'recommends runtime interop over lossy translation') with no vague filler. Imperative/third-person voice, so no voice penalty applies.

3 / 3

Completeness

Explicitly answers what ('Port an existing Remotion composition to HyperFrames HTML') and when ('Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source') plus an enumerated Do-NOT-use list, satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

Covers the natural verbs users would say ('port/convert/migrate/translate a Remotion source') alongside the product nouns 'Remotion' and 'HyperFrames', giving good coverage of real trigger phrasing.

3 / 3

Distinctiveness Conflict Risk

Carves a narrow one-way Remotion→HyperFrames niche, names the sibling skills to defer to (`/general-video`, `/hyperframes`), and enumerates out-of-scope sources (After Effects, Framer Motion, plain React/CSS) and the reverse direction, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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
calesthio/OpenMontage
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.