CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frost-sequence-camera-orbit

An orbiting camera follows an ice logo as it breaks apart, reforms into two text moments, and fades. HyperFrames block, 1920×1080, 22.5s, 216 variables.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./registry/blocks/frost-sequence-camera-orbit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 exceptionally actionable — every workflow step is a copy-paste command, and the runtime contract and editing rules are precise and non-obvious. Its weaknesses are structural: the 216-row variables table is a monolith that belongs in a separate reference file (and its cell values contain unescaped pipes that break the markdown table rendering), and the headline composition file listed in the Files section is missing from the bundle.

Suggestions

Move the 216-row variable table to a reference file (e.g. `references/variables.md`) and keep a short categorized summary in SKILL.md (e.g. "Material, Break, Flight, Return, Light, Post groups — full table in references/variables.md").

Escape or replace the literal pipe characters in cell values (e.g. `"Hard to|break."`, enum lists like `physical|directed|hybrid`) — they currently split cells and break the markdown table rendering.

Add a post-install verification step (e.g. confirm `compositions/frost-sequence-camera-orbit/frost-sequence-camera-orbit.html` exists) and clarify why the primary HTML file is absent from the skill bundle, or include it.

DimensionReasoningScore

Conciseness

The prose sections are lean with no concept over-explanation, but the inline 216-row variable table consumes roughly three quarters of the body's tokens and loads on every skill invocation even when customization is not the task; the opening paragraph also restates the frontmatter description. Anchor 3 ("could be tightened") fits better than 4, and nothing pads or explains known concepts, so it is not a 2.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: `npx hyperframes add frost-sequence-camera-orbit`, a complete data-composition-* mount snippet, and `npx --yes hyperframes@0.8.12 render ... --variables '{"headline1":"Hard to|break."}'` with a concrete customization example, plus exact runtime APIs (`window.__hyperframes.getVariables()`, `window.__timelines["frost-sequence-rig"]`). The common cases — install, embed, custom render — are all covered.

5 / 5

Workflow Clarity

Files → Install → mount → render → editing rules is a clear, unambiguous sequence with exact commands at each step. It falls short of anchor 5 because there are no validation checkpoints or error-recovery guidance (e.g. verifying installed files or a rendered test frame), though the non-destructive nature means the 3-cap does not apply.

4 / 5

Progressive Disclosure

Sections are clearly organized and the bundle is genuinely one level deep (assets/ with 16 real files matching the listing), but ~220 lines of variable reference are inlined in SKILL.md instead of split into an on-demand reference file, and the primary listed file `frost-sequence-camera-orbit.html` (131 KB) is absent from the actual bundle. This matches anchor 3 — real structure present, but content that should be separate is inline.

3 / 5

Total

15

/

20

Passed

Description

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

The description is highly distinctive and concrete about the artifact's specs, but it reads as a content synopsis rather than a capability statement, and it omits any usage trigger guidance. Adding an explicit "Use when..." clause with natural trigger phrases would lift both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding a 3D ice/frost logo reveal, shatter-and-reform intro, or frozen text sequence to a HyperFrames composition."

State the skill's capabilities as actions rather than only describing the artifact: "Adds and renders a customizable..." (install, embed, render with custom variables).

Include natural synonyms users would say — shatter, frost, freeze, 3D intro, logo reveal — so the description matches how the need is actually voiced.

DimensionReasoningScore

Specificity

"An orbiting camera follows an ice logo as it breaks apart, reforms into two text moments, and fades. HyperFrames block, 1920×1080, 22.5s, 216 variables" gives concrete artifact specifics (resolution, duration, variable count) but lists no capability actions (no add/render/customize verbs), matching anchor 3 rather than 4; it is far too concrete for anchor 2.

3 / 5

Completeness

The "what" is clear (a 22.5s ice-logo shatter/reform sequence as a HyperFrames block), but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural domain phrases like "ice logo", "breaks apart", and "orbiting camera" are present, but common variations users would say (shatter, frost, freeze, 3D intro, logo reveal) are missing, which is exactly anchor 3.

3 / 5

Distinctiveness Conflict Risk

"HyperFrames block, 1920×1080, 22.5s, 216 variables" carves out an unmistakable niche with essentially zero overlap risk; the anti-drift check against anchor 4 fails because no closely related skill could plausibly collide with this description.

5 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing, 6 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

heygen-com/hyperframes

Path

registry/blocks/frost-sequence-camera-orbit/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.