CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is motion-doctrine in heygen-com/hyperframes

SKILL.md
Quality
Evals
Security

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.

Excellent doctrine-style skill body: a clearly sequenced authoring workflow with a real verification gate and error-recovery loops, copy-paste-ready commands, and precise numeric parameters, with details properly pushed to a one-level reference file and scripts. The only minor trim opportunity is the Anti-Patterns table's recap of previously stated rules.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no basic concepts are explained, and rules are delivered as terse parameters ("Exit ≈ 75% of entry", "Total stagger ≤ 500ms", "back.out(1.4–1.7)"). It is not 5 because the Anti-Patterns table recapitulates rules already stated in Part 1/Part 2 (e.g., the vector-law and idle-wobble rows), a minor duplication that could be trimmed; it is well above 3 because nearly every token carries a rule, parameter, or command.

4 / 5

Actionability

Fully executable guidance: copy-paste-ready commands with flags ("node <SKILL_DIR>/scripts/seam-stamp.mjs --ledger ledger.json --write index.html", "seam-gate.mjs verify --ledger ledger.json --project ."), exact numeric specs ("Single entry ≤ ~800ms", "0.3–0.75s pause", "entry ~127% of exit"), named eases ("power4.in + power4.out"), and a concrete artifact (ledger.json with its schema in references/seam-gate.md). Common cases are covered by the route table and the sustained-motion routes.

5 / 5

Workflow Clarity

The authoring order is an explicit sequenced pipeline ("vector ledger (ledger.json) → STAMP the master seams... → VERIFY (scripts/seam-gate.mjs)") with a hard validation gate ("exit 0 or the seam is not done") and genuine error-recovery feedback loops: "Edits re-open the seam... re-run the verifier", "A VO regen re-opens its seams", and the clip-gating gotcha diagnosing the usual zero-overlap FAIL. The Anti-Patterns table doubles as a checklist.

5 / 5

Progressive Disclosure

The body stays at doctrine level and clearly signals one-level-deep bundle references that exist and are appropriately scoped: "(schema: references/seam-gate.md)" and "(usage + ledger schema: references/seam-gate.md)" — verified as a real 97-line file with no nested .md references — plus the two scripts, and a route map delegating mechanics to the technique skills. Navigation is easy and nothing that belongs in a reference is inlined.

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, highly specific gateway description that explicitly answers what it covers and when to load it, with a clear niche and explicit supersede semantics. Its only deductions are the imperative "load FIRST" voice (voice penalty on specificity) and a few missing natural trigger synonyms.

DimensionReasoningScore

Specificity

The description comprehensively enumerates concrete covered capabilities ("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... the ban on idle wobble... stillness-before-climax, and the sustained-motion routes") plus routing to three named technique skills — a base-5 list. However, the opening "GATEWAY — load FIRST before composing" is imperative/implicit second-person voice, which the rubric penalizes by 1, giving 4. It is not 3 because the what is far more than 1-2 concrete actions.

4 / 5

Completeness

Both what and when are explicitly and concretely answered: the when is "GATEWAY — load FIRST before composing any HyperFrames animation or video" and the what is "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", followed by an explicit coverage list and trigger keywords. Not 4 because the when-clause is already explicit and concrete, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Good keyword coverage with natural domain terms a user composing animation would say: "continuity, direction, vector, momentum, seam, transition, ease, performance, idle-motion, narrative-motion, film-grammar", plus "HyperFrames animation", "video", and "camera move". It falls short of 5 because a few natural phrasings (e.g., "camera movement", "cuts", "easing", "animation timing") are absent; it is above 3 because coverage is broad and domain-appropriate rather than partially missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche with minimal conflict risk: it is scoped to "HyperFrames animation or video", explicitly states "These rules SUPERSEDE generic / upstream motion guidance", and names its distinct downstream skills ("cut-the-curve... oversized-cursor, seam-craft"), so it is unlikely to trigger for the wrong skill. Not 4 because no meaningful overlap with neighboring skills is left unstated.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

.claude/skills/motion-doctrine/SKILL.md

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.