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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is an efficient, well-structured doctrine document: concrete rules, a crisp injector sequence, and a useful token table, all free of padding. Its weaknesses are mild — embedded dated observations instead of isolated provenance notes, and verification expressed as past-tense assertions rather than actionable validation steps.

Suggestions

Move dated provenance (the 2026-05-31 prototype render, the Spotify white-flash observations, the 'now emits' assembler change) into a short 'Verification history / old patterns' section so the doctrine itself stays time-free.

Add explicit validation checkpoints the reader can run (e.g., a lint or render check to confirm #root background and track ping-pong after assembly) instead of only retrospective 'verified by' citations.

Give the transition-registry pointer a concrete path or file name so navigation to the per-transition catalog is unambiguous.

Dimension	Reasoning	Score
Conciseness	Lean and dense with no filler or explanation of concepts Claude already knows; every section carries project-specific mechanics. Not 5 because time-sensitive details ("observed on two Spotify runs before the fix", "Verified by prototype render (2026-05-31)", "assemble-index.mjs now emits") are woven into the doctrine rather than isolated in a dated/deprecated section.	4 / 5
Actionability	Concrete, usable guidance: a copy-paste CSS guard ("#root { background: var(--canvas-deep, var(--canvas, #000)) }"), a numbered four-step injector sequence, a complete placeholder-token table, and file:line citations. Not 5 because no complete executable template example is shown inline (delegated to the transition registry), leaving minor gaps for a reader reproducing the mechanics.	4 / 5
Workflow Clarity	The injector sequence (extend duration, pull start earlier, ping-pong track indices, stamp template) is clearly ordered and constraint-checked against lint rules. Not 5 because validation appears as retrospective assertions ("Verified by prototype render", "verified: core/src/runtime/init.ts:1393-1410") rather than explicit checkpoints or feedback loops the reader executes.	4 / 5
Progressive Disclosure	No bundle files exist, and the ~64-line body is cleanly sectioned with a single clearly signaled external pointer ("the per-transition catalog... lives in the transition registry"), keeping navigation easy. Not 5 because the body slightly exceeds the under-50-line threshold where organization alone earns full marks, and the registry pointer names no concrete path.	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 strong description: it defines a precise niche, provides concrete trigger conditions including symptom-based ones, and explicitly bounds what it does not cover. Its only weakness is jargon-heavy phrasing that slightly narrows natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete, domain-specific capabilities ("overlaps wrappers, holds final frames, ping-pongs tracks, and stamps lint-clean template code", "opaque stage-ground (#root background) white-flash guard") with only minor coverage gaps. It does not reach 5 because the actions are stated as covered mechanisms rather than a fully comprehensive action list, and it stays below 5's exhaustive coverage.	4 / 5
Completeness	Explicitly answers both: the "what" ("Render-correctness doctrine for scene-to-scene seams... the prerequisites that make transitions composite correctly") and the "when" via a concrete "Load when..." clause with four distinct triggers, plus an explicit negative boundary ("Does NOT contain the per-transition catalog"). Clearly matches the 5 anchor rather than 4, whose 'when' is less explicit.	5 / 5
Trigger Term Quality	Natural symptom phrases a user would say are present ("when a white flash appears at a cut or crossfade seam", "assembling the master timeline / index.html", "transition opacity dip shows through"). Not 5 because coverage leans on project-specific jargon (ping-pong, Tier-B, gsap_template) and misses common synonym variations.	4 / 5
Distinctiveness Conflict Risk	Clear niche (HyperFrames launch-video scene seams on the master timeline) with distinct triggers and an explicit pointer directing per-transition lookups to the registry instead. Minimal conflict risk with any generic skill.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: heygen-com/hyperframes
Path: .agents/skills/seam-craft/SKILL.md
Commit: a4a7cbe

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.