CtrlK
BlogDocsLog inGet started
Tessl Logo

seam-craft

Render-correctness doctrine for scene-to-scene seams in HyperFrames launch videos — the prerequisites that make transitions composite correctly on the master timeline. Load when assembling the master timeline / index.html, when a white flash appears at a cut or crossfade seam (especially on dark films), when reasoning about why a transition opacity dip shows through, or when verifying the render-side mechanics of how overlapping scene wrappers blend. Covers the opaque stage-ground (#root background) white-flash guard and how the injector overlaps wrappers, holds final frames, ping-pongs tracks, and stamps lint-clean template code onto the master timeline. Does NOT contain the per-transition catalog — see the transition registry for individual transition entries.

68

Quality

81%

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

75%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.

A dense, well-organized doctrine page with concrete CSS and injector mechanics anchored by source citations. It is slightly let down by time-stamped asides and the absence of an explicit render-verification feedback loop.

Suggestions

Move the dated prototype-verification notes (e.g. 'Verified by prototype render (2026-05-31)') into a verification/deprecated section or strip the dates to keep the body evergreen and improve conciseness.

Add an explicit validate→fix→retry loop for the render check (e.g. 'after assembling, render the seam; if a white flash returns, confirm #root background is painted and re-render') to lift workflow clarity.

Show one complete sample gsap_template line with tokens substituted to make the placeholder table fully copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — no generic explanations of compositing or GSAP — but a few token-dense tables and date-stamped prototype notes ('Verified by prototype render (2026-05-31)') could be trimmed; not a 5 because of those time-sensitive asides.

4 / 5

Actionability

Gives a concrete executable CSS rule ('#root { background: var(--canvas-deep, var(--canvas, #000)) }'), numbered injector steps with file:line citations, and a placeholder token table — mostly copy-paste ready with minor gaps around the actual gsap_template lines.

4 / 5

Workflow Clarity

The injector-application sequence is clearly numbered with an explicit same-track-overlap guard and source-verified checkpoints, but there is no validate/fix/retry feedback loop around the render verification step.

4 / 5

Progressive Disclosure

Well-structured with section headers and a clear hand-off ('per-transition catalog lives in the transition registry'); no bundle files present, so structure is internal only — good but a single inline body rather than the ideal one-level-deep reference split.

4 / 5

Total

16

/

20

Passed

Description

87%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 highly specific, well-scoped doctrine description with explicit load-when triggers and a clear negative boundary. Trigger terms lean domain-technical, slightly limiting how naturally a user would phrase them.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'overlaps wrappers, holds final frames, ping-pongs tracks, and stamps lint-clean template code' plus the stage-ground guard — covering the doctrine comprehensively with no abstract filler.

5 / 5

Completeness

Explicitly answers what ('Render-correctness doctrine … prerequisites that make transitions composite correctly') and when ('Load when assembling…', 'when a white flash appears…', 'when reasoning about…'), plus a clear boundary note on what it does NOT contain.

5 / 5

Trigger Term Quality

Strong natural triggers ('assembling the master timeline / index.html', 'a white flash appears at a cut or crossfade seam', 'opacity dip shows through') cover the main user-utterable phrases, but domain jargon dominates over everyday synonyms and file extensions.

4 / 5

Distinctiveness Conflict Risk

Niche triggers tied to HyperFrames/PLV seams and a stated negative boundary ('Does NOT contain the per-transition catalog') keep it distinct from neighboring transition-registry skills.

5 / 5

Total

19

/

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.