From d839fd40170ee3007f3aed9eb62d9816960286ec Mon Sep 17 00:00:00 2001 From: James Date: Sat, 9 May 2026 01:33:44 +0000 Subject: [PATCH] fix(skills): shorten remotion-to-hyperframes description under 1024 chars The agent skill loader rejects SKILL.md files whose frontmatter description exceeds 1024 characters, so remotion-to-hyperframes was being skipped at startup with a "exceeds maximum length of 1024 characters" warning. Trimmed the description from 1240 to 896 characters by collapsing the trigger-phrase examples and tightening prose, while preserving every trigger / no-trigger guardrail. Moved the detailed list of trigger phrases and the 4 negative cases into a new "## When to use" section in the body so the guidance is not lost. Fixes #688 --- skills/remotion-to-hyperframes/SKILL.md | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/skills/remotion-to-hyperframes/SKILL.md b/skills/remotion-to-hyperframes/SKILL.md index 4deea5518..9cca4eb93 100644 --- a/skills/remotion-to-hyperframes/SKILL.md +++ b/skills/remotion-to-hyperframes/SKILL.md @@ -1,6 +1,6 @@ --- name: remotion-to-hyperframes -description: Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition. Use ONLY when the user explicitly asks to port, convert, migrate, translate, or rewrite a Remotion composition as HyperFrames — for example "port my Remotion project to HyperFrames", "convert this Remotion code to HyperFrames", "migrate from Remotion", "translate this Remotion comp", or "rewrite this as HyperFrames HTML". Do NOT use when (a) the user is authoring a NEW HyperFrames composition, even if they have or are A/B-testing a similar Remotion video; (b) the user mentions Remotion in passing without asking for migration; (c) the user shares Remotion code as reference material rather than asking for a translation; (d) the user asks for "the same video as my Remotion one" without explicitly asking to migrate the source — treat that as a fresh HyperFrames build. When in doubt, default to authoring a native HyperFrames composition with the `hyperframes` skill instead. Skill detects unsupported patterns (useState, useEffect with side effects, async calculateMetadata, third-party React component libraries, `@remotion/lambda` features) and recommends the runtime interop escape hatch instead of attempting a lossy translation. +description: Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition. Use ONLY when the user explicitly asks to port, convert, migrate, translate, or rewrite a Remotion composition as HyperFrames (e.g. "port my Remotion project to HyperFrames"). Do NOT use when (a) authoring a NEW HyperFrames composition (even if A/B-testing a Remotion video); (b) Remotion is mentioned in passing; (c) Remotion code is shared as reference, not for translation; (d) the user wants "the same video as my Remotion one" without explicitly asking to migrate the source — treat as a fresh HyperFrames build. When in doubt, default to the `hyperframes` skill. Detects unsupported patterns (useState, useEffect side effects, async calculateMetadata, third-party React component libraries, `@remotion/lambda`) and recommends the runtime interop escape hatch instead of a lossy translation. --- # Remotion to HyperFrames @@ -11,6 +11,25 @@ Translate Remotion (React-based) video compositions into HyperFrames (HTML + GSA The skill ships with a **tiered test corpus** (T1–T4, 4 fixtures total) that grades translations against measured SSIM thresholds. Don't translate without running the eval — a translation that "looks right" but renders 0.05 SSIM lower than the validated baseline is silently wrong. +## When to use + +**Use this skill ONLY when the user explicitly asks to migrate from Remotion.** Example trigger phrases: + +- "port my Remotion project to HyperFrames" +- "convert this Remotion code to HyperFrames" +- "migrate from Remotion" +- "translate this Remotion comp" +- "rewrite this as HyperFrames HTML" + +**Do NOT use this skill when:** + +- (a) The user is authoring a **new** HyperFrames composition, even if they have or are A/B-testing a similar Remotion video. +- (b) The user mentions Remotion in passing without asking for migration. +- (c) The user shares Remotion code as reference material rather than asking for a translation. +- (d) The user asks for "the same video as my Remotion one" without explicitly asking to migrate the source — treat that as a fresh HyperFrames build. + +When in doubt, default to authoring a native HyperFrames composition with the `hyperframes` skill instead. + ## Workflow ### Step 1: Lint the source