CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figma

Bring Figma into a HyperFrames video - rendered assets, brand tokens, components, storyboard frames as reconstructed motion (frames read as states, not slides), shaders and connector-assisted motion. Use when the person pastes a figma.com link or asks to use a Figma design, frame, logo or brand.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

An exceptionally lean, dense, and executable skill body: full CLI syntax, real bundle scripts, explicit validation with feedback loops, and no filler. The only structural nit is that a few secondary details (connector-binding schema, beacon bookkeeping) are inlined rather than split into a reference file.

DimensionReasoningScore

Conciseness

Every sentence carries operational payload — flags, thresholds ("fails under 15 dB", "batches of about 4 scene frames"), fallbacks, and exact error semantics — with zero padding and no explanation of concepts Claude already knows. Nothing can be cut without losing information, which is the anchor-5 profile rather than anchor 4's "minor instances of over-explanation".

5 / 5

Actionability

Commands are copy-paste ready with full argument shapes ("npx hyperframes figma asset '<url or fileKey:nodeId>' [more refs] --format svg|png --scale 2 --description ... [--entity ...]", "node <SKILL_DIR>/scripts/verify-motion.mjs --reference <export.mp4> --render <render.mp4> --crop WxH+X+Y"), the script exists in the bundle with matching flags, and named library functions (motionContextToDocs, motionToGsap, emitTimelineScript) are given with module paths and option semantics. It is not anchor 4 because the concrete commands already cover the common cases end to end.

5 / 5

Workflow Clarity

Both multi-step workflows (Motion, Storyboards) are numbered and sequenced, with explicit validation and feedback loops: token pre-check with a stop condition, an error table mapping each failure to a recovery action, and a verification step with a threshold plus interpretation guidance ("A fail means fix the translation, not the threshold"). Batch limits ("past about 12 ids /v1/images times out") and the REQUIRES_ENTERPRISE non-failure note round out checkpoint coverage.

5 / 5

Progressive Disclosure

Sections are clear, the heavy verification logic is correctly offloaded to scripts/verify-motion.mjs, and the one external pointer (plugin-installation.md) is a clearly signaled one-level link. It falls short of anchor 5 because secondary detail is inlined in the main file — notably the connector-bindings JSONL schema inside the tokens bullet and the beacon variants — where a references/ file for the motion/storyboard deep-dives would ease navigation; this matches anchor 4's "minor organization gaps".

4 / 5

Total

19

/

20

Passed

Description

92%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 description: concrete, comprehensive capability list plus an explicit, naturally-phrased trigger clause in third person. The only weakness is slightly thin synonym coverage (no "prototype", "mockup", or "Figma file").

DimensionReasoningScore

Specificity

The description enumerates the skill's full capability set — "rendered assets, brand tokens, components, storyboard frames as reconstructed motion (frames read as states, not slides), shaders and connector-assisted motion" — concrete items that map one-to-one onto every section of the body, with no coverage gaps. It stays at anchor 5 rather than 4 because the coverage is comprehensive, not just "several actions with minor gaps".

5 / 5

Completeness

Both halves are explicit: the "what" ("Bring Figma into a HyperFrames video - rendered assets, brand tokens, components, ... shaders and connector-assisted motion") and the "when" ("Use when the person pastes a figma.com link or asks to use a Figma design, frame, logo or brand") with concrete trigger phrases, matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

"Use when the person pastes a figma.com link or asks to use a Figma design, frame, logo or brand" covers the most natural triggers well, including the URL-paste case. It sits at 4 rather than 5 because common variations like "Figma file", "prototype", or "mockup" are absent.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (Figma-to-HyperFrames import) with distinct, domain-qualified triggers ("figma.com link", "Figma design, frame, logo or brand"), so it is unlikely to fire for unrelated skills; "logo or brand" is safely qualified by "Figma".

5 / 5

Total

19

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

heygen-com/hyperframes

Path

skills/figma/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.