CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orbit-card

A single feature card orbits a dot sphere on approved Blender camera motion. HyperFrames block, 1920×1080, 10s, 4 variables.

Quality

81%

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

96%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 exemplary lean composition README: copy-paste-ready install, mount, and render commands, a precise variables table, and a runtime contract with non-obvious constraints (seek-safety, closed-form animation, no Date.now). The only improvement space is a slightly tighter distinction between runtime assets and user-editable surfaces in the file manifest.

DimensionReasoningScore

Conciseness

Every section carries project-specific, non-obvious information — the approved-timing overview, the file manifest with sizes, the install/mount/render commands, the variables table, and three non-generic editing rules — with no tutorial filler or explanation of concepts Claude already knows. "Lean and efficient; every token earns its place."

5 / 5

Actionability

Guidance is fully executable: "npx hyperframes add orbit-card", a complete copy-paste mount <div> with all data-* attributes, a render command with a concrete --variables JSON payload, and a variables table giving types, defaults, and the -36000–36000 range for cardOrbitDegrees. The common install/mount/customize cases are all covered.

5 / 5

Workflow Clarity

The install → mount → render sequence is linear and unambiguous with concrete commands at each step, and the variables section explains runtime access precisely. As a single-purpose, non-destructive skill, the simple-skill exception applies: the one action (install and mount the composition) is unambiguous with no risky operations requiring validation checkpoints.

5 / 5

Progressive Disclosure

Well-organized sections (Files, Install, Variables, Runtime contract, Editing rules) with a manifest that matches the actual assets/ bundle file-for-file. Docked one point because the body runs ~68 lines (above the under-50-lines guideline for an unqualified 5) and the large runtime assets (orbit-motion.js 59 KB, orbit-scene.js 8 KB) are listed only by size, with no one-line note distinguishing hands-off runtime files from the files a user would actually edit — a minor organization gap per the anchor "most content is appropriately placed... minor organization gaps".

4 / 5

Total

19

/

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 concise, concrete, and highly distinctive for its niche, but it functions as a composition spec rather than a skill description: it has no explicit trigger guidance and lacks natural keyword variations a user might say. Adding a "Use when..." clause would resolve the biggest gap.

Suggestions

Add an explicit trigger clause, e.g. "Use when adding or rendering HyperFrames compositions in a host page, or when animating a feature card around a 3D object."

Include natural trigger terms and variations users would actually say — "HyperFrames composition", "animation block", "orbit animation", ".html composition" — alongside the existing jargon.

State the actionable capability in third person (e.g. "Renders and mounts an orbiting feature-card composition...") rather than only describing what the artifact looks like.

DimensionReasoningScore

Specificity

"A single feature card orbits a dot sphere on approved Blender camera motion. HyperFrames block, 1920×1080, 10s, 4 variables" names the domain and concrete specs (resolution, duration, variable count), but describes a composition rather than listing actions — more concrete than the anchor-2 example "Processes PDF files" yet not the comprehensive multi-action coverage of anchors 4–5.

3 / 5

Completeness

The "what" is clear (an orbiting feature-card composition block with specs), but there is no "Use when..." or equivalent trigger guidance, which per the judging guidelines caps completeness at 3: "Has a clear 'what' but 'when' is missing or only weakly implied".

3 / 5

Trigger Term Quality

Relevant keywords are present ("HyperFrames", "Blender", "orbit", "feature card") but coverage stops there — no synonyms, natural user phrasings, or file extensions (e.g. .html, animation, motion-graphics), matching the anchor "Some relevant keywords but missing common variations or synonyms".

3 / 5

Distinctiveness Conflict Risk

"HyperFrames block" and "approved Blender camera motion" carve out a clear niche with distinct triggers; virtually no other skill would fire on this description, matching "Clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

heygen-com/hyperframes

Path

registry/blocks/orbit-card/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.