CtrlK
BlogDocsLog inGet started
Tessl Logo

cut-the-curve

The technique catalog: five velocity-matched SEAMS (zoom-through, INVERSE zoom-through, cut-the-curve, waterfall cut, rack-focus blur-cut) plus the two in-scene techniques — waterfall ENTRY (staggered arrival cascades for title cards / segment openers) and the nudge curve (slow-fast-slow three-phase group slides). Covers partial-travel (~12% of frame) velocity matching via mirrored power4 eases, the Z scale-sign rule, size-scaled blur (10px text / 18-20px full-frame), word-by-word staggered cuts, cascade pacing by element weight, and the 10/65/25 slide ratio. Read before authoring any transition, text-beat handoff, kinetic text entry, or group reposition. [depth, zoom, inverse-zoom, scale-sign, mirrored-zoom, rack-focus, pacing, velocity, cut-the-curve, waterfall, stagger, cascade, kinetic-text, title-card, segment-opener, nudge, slide, easing, group-motion, z-depth, motion-graphics, cinematic, transition, blur, directional-continuity]

69

Quality

87%

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 well-crafted parameter reference: token-dense tables, exact values, clear technique selection, and an anti-patterns checklist, with deferred code keeping the body lean. The main gaps are the unresolvable `examples/gsap-implementation.md` pointer and duplicated comparison tables that could be merged.

Suggestions

Ship `examples/gsap-implementation.md` in the bundle (or inline one complete cut-the-curve GSAP timeline) so the "Code" section's pointer resolves — actionability currently rests on a file not present.

Merge the opening "Catalog" table with the near-duplicate "Choosing a Variant" table (they repeat scope/axis/travel/eases) into a single selection table.

State where `motion-doctrine` and `seam-craft` live (sibling skill paths) so the "read it first" instruction is actionable from this skill alone.

DimensionReasoningScore

Conciseness

The body is dense parameter tables with no filler — it assumes GSAP knowledge, never explaining what a library or ease is, and every section carries exact values (e.g. "±230px (~12% frame)", "0.34s power4.in", "0.05s × 0.84 decay"). It falls short of 5 because content is duplicated: the "Choosing a Variant" table largely restates the opening "Catalog" table, and the Anti-Patterns table repeats rules already given in sections 1–7.

4 / 5

Actionability

Guidance is highly concrete — exact eases, durations, scales, blur peaks, opacity values, and stagger timings per technique, enough to author the tweens directly. Not a 5 because the body contains zero executable code and its sole code pointer ("All GSAP code templates... live in `examples/gsap-implementation.md`") targets a file that does not exist in this bundle, leaving a minor but real gap between parameters and a copy-paste-ready template.

4 / 5

Workflow Clarity

A reference catalog rather than a linear procedure, but it sequences use well: an ordered reading path ("read it first" → motion-doctrine), a catalog with a "Use for" column, a "Choosing a Variant" decision table, and an Anti-Patterns checklist that functions as verification before shipping. Not a 5 because there are no worked end-to-end examples or explicit checkpoints tying the pieces into one authoring pass.

4 / 5

Progressive Disclosure

Good structure: parameters inline in SKILL.md, with clearly signaled one-level-deep pointers ("motion-doctrine", "seam-craft", "examples/gsap-implementation.md") that keep the body lean. Docked from 5 because no bundle files exist (no references/, scripts/, assets/, or examples/), so the load-bearing `examples/gsap-implementation.md` reference cannot be resolved — navigation depends on files outside this bundle.

4 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: names every technique, states the governing parameters concretely, and closes with an explicit "Read before..." trigger clause backed by a rich synonym list. The only weakness is that it sits inside a family of sibling motion skills and a few of its trigger terms are broad enough to compete with them.

DimensionReasoningScore

Specificity

The description enumerates all seven techniques by name ("zoom-through, INVERSE zoom-through, cut-the-curve, waterfall cut, rack-focus blur-cut", "waterfall ENTRY", "nudge curve") plus concrete parameters ("partial-travel (~12% of frame)", "mirrored power4 eases", "10px text / 18–20px full-frame", "10/65/25 slide ratio") — multiple specific concrete capabilities with comprehensive coverage, matching the 5 anchor. It is not a 4 because coverage of what the skill contains is exhaustive rather than having minor gaps.

5 / 5

Completeness

"What" is answered explicitly (the full technique catalog with its parameters) and "when" is an explicit trigger clause: "Read before authoring any transition, text-beat handoff, kinetic text entry, or group reposition." Both are concrete and explicit, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

The bracketed keyword list ("transition, blur, waterfall, stagger, cascade, kinetic-text, title-card, segment-opener, nudge, slide, easing, group-motion, cinematic, pacing, velocity...") plus natural phrases in the prose ("title cards / segment openers", "group reposition") give comprehensive coverage with many synonyms a user authoring motion would actually say. Not a 4: no obvious natural variant is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (velocity-matched seam parameters within a motion system) with distinctive triggers like "cut-the-curve", "rack-focus", and "scale-sign". However the body reveals closely related sibling skills ("motion-doctrine", "seam-craft") sharing this motion territory, and broad tags like "transition", "easing", and "pacing" create minor overlap risk with those siblings — matching the 4 anchor ("mostly distinct; minor overlap risk with closely related skills") rather than 5.

4 / 5

Total

19

/

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