motion-doctrine

GATEWAY — load FIRST before composing any HyperFrames animation or video. The high-level motion law that makes a multi-scene video feel like ONE continuous camera move instead of a stack of independently-animated slides. Covers the vector law (how you exit determines how you enter, incl. the Z scale-sign rule), the film's current, carrier elements, causal motion, the Seam Gate (build-gate enforcement), the ban on idle wobble (motion must PERFORM, not breathe), stillness-before-climax, and the sustained-motion routes. Routes to the low-level technique skills (cut-the-curve — the full catalog incl. waterfall entry + nudge curve, oversized-cursor, seam-craft). These rules SUPERSEDE generic / upstream motion guidance. [continuity, direction, vector, momentum, seam, transition, ease, performance, idle-motion, narrative-motion, film-grammar]

Quality

90%

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

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

An exceptionally well-crafted instruction skill: fully executable commands with concrete numeric guidance, an explicitly sequenced workflow with a build-gate validation checkpoint and error-recovery loops, and clean one-level-deep progressive disclosure verified against the actual bundle. The only weakness is mild redundancy between the Anti-Patterns table and the preceding sections.

Dimension	Reasoning	Score
Conciseness	The body is dense, project-specific doctrine with essentially no explanation of concepts Claude already knows — every rule is unique to this motion system. The one trimmable piece is the Anti-Patterns table (~15 lines), which largely restates rules already given in Part 1 and Part 2 in Don't/Instead form, so not every token earns its place. Not 3: the rest is lean and high-signal with no padding.	4 / 5
Actionability	Commands are copy-paste ready ('node <SKILL_DIR>/scripts/seam-stamp.mjs --ledger ledger.json --write index.html', 'seam-gate.mjs probe --t <cut>') and the guidance carries concrete numeric values throughout — entry ≤ ~800ms, exit ≈ 75% of entry, 0.3–0.75s stillness pause, 'set initial autoAlpha: 0 AND data-start = the cut time', forbidden eases, per-seam stamp options. Common cases are covered.	5 / 5
Workflow Clarity	The authoring order is an explicit sequenced pipeline (vector ledger → STAMP master seams → sustained-motion route → carriers/causes → build comps → VERIFY), with a hard exit-0 validation gate, error-recovery feedback loops ('Edits re-open the seam... re-run the verifier', 'A VO regen re-opens its seams'), and troubleshooting for the usual failure ('Clip-gating gotcha... the usual cause of a zero-overlap FAIL').	5 / 5
Progressive Disclosure	The body acts as a gateway overview with a route map to the implementation skills, and correctly offloads script usage and the ledger schema to references/seam-gate.md (a real file that matches its description), referenced one level deep and clearly signaled at both mention sites. The scripts referenced (seam-stamp.mjs, seam-gate.mjs) exist in the bundle.	5 / 5
	Total	19 / 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, information-dense description with an explicit when-clause, comprehensive concrete coverage, and a clearly delineated gateway niche. The only deductions are the second-person phrasing inside the vector-law parenthetical and a trigger-keyword list that leans toward domain jargon over natural user phrasings.

Suggestions

Rewrite the parenthetical '(how you exit determines how you enter, incl. the Z scale-sign rule)' in third person (e.g. 'the exit vector determines the entry vector, incl. the Z scale-sign rule') to keep the description in third-person voice.

Add plain natural trigger terms such as 'animation', 'video', and 'motion design' to the keyword list, and drop or pair jargon-only entries like 'narrative-motion' and 'film-grammar' with plainer synonyms.

Dimension	Reasoning	Score
Specificity	The description comprehensively names concrete capabilities (vector law with Z scale-sign rule, the film's current, carrier elements, causal motion, the Seam Gate build-gate enforcement, the idle-wobble ban, stillness-before-climax, sustained-motion routes), matching the 5-anchor — but the second-person phrasing 'how you exit determines how you enter' triggers the rubric's explicit third-person-voice penalty, reducing it by 1. Not 3: coverage is comprehensive, far beyond '1-2 concrete actions'.	4 / 5
Completeness	Both halves are explicit: the 'what' ('The high-level motion law that makes a multi-scene video feel like ONE continuous camera move instead of a stack of independently-animated slides') and the 'when' ('load FIRST before composing any HyperFrames animation or video') with concrete trigger conditions and routes to the technique skills.	5 / 5
Trigger Term Quality	The bracketed list includes genuinely natural terms (continuity, direction, transition, ease, seam, performance), but several entries are domain jargon a user would not naturally say ('narrative-motion', 'idle-motion', 'film-grammar'), and the plainest natural triggers ('animation', 'video', 'motion') appear only in prose, not the keyword list. Not 5 because coverage of natural phrasings is incomplete; not 3 because the terms that are there are relevant and several are natural.	4 / 5
Distinctiveness Conflict Risk	It carves out a clear niche — a HyperFrames-specific motion-doctrine gateway that explicitly routes to named technique skills (cut-the-curve, oversized-cursor, seam-craft) and states 'These rules SUPERSEDE generic / upstream motion guidance', minimizing overlap with generic motion/animation skills.	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/motion-doctrine/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.