CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hyperframes-registry

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Quality

95%

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

93%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 lean, highly actionable body: copy-paste commands for search, install, variables, beats, and gap reporting, with details correctly delegated to real, well-labeled one-level-deep reference files. The only meaningful gap is that the find->install->wire sequence is conveyed by section order rather than explicit steps, and batch installs (`add <tag>`) lack a stated post-install verification checkpoint beyond the printed file list.

DimensionReasoningScore

Conciseness

The body is dense with operational facts and zero conceptual padding: "npx hyperframes catalog --query ... --json", "add needs the network even for an item installed before; search works offline from the cached manifest", "Keep an installed item's ids prefixed as they are, so two items can't collide". It never explains concepts Claude already knows (what HTML, compositions, or timelines are) and every line carries a rule, command, or pointer. It matches anchor 5 ('lean and efficient; assumes Claude's competence; every token earns its place') rather than 4, which reserves room for trimmable over-explanation — the only candidate, "Starting from an item is faster and usually better", is a one-sentence orientation that sets decision policy (prefer installed items over hand-building), not padding.

5 / 5

Actionability

Every workflow step ships a copy-paste command: `npx hyperframes catalog --query "..." --json`, `npx hyperframes add <name> --json` ("prints the written files and the mount snippet"), `add --vars '{"title":"…"}'`, `npx hyperframes beats --json`, and a pre-filled gap-report command: `npx hyperframes feedback --search-miss "<query>" --wanted "<the move you needed>" --tier <tier>`. Wiring guidance is equally concrete (specific data attributes: data-composition-src, data-composition-id, data-start, data-duration, data-variable-values). This matches anchor 5 ('fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

The find -> install -> wire -> edit sequence is legible through section order ("Find and install", "Wiring") with a feedback loop for search misses ("Nothing fits: report it before you hand-build") and built-in output feedback ("add ... prints the written files and the mount snippet"). However, the sequence is implied by headings rather than explicitly ordered, and there are no verification checkpoints after batch installs (`add <tag>` "installs every block with that tag") beyond the printed file list. This fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') — above 3 because checkpoints are partially present (gap reporting, printed output, id-collision rule), below 5 because there is no explicit validate-after-install step for batch operations.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview: the core loop and wiring essentials live inline, while details are pushed one level deep into clearly signaled, topically labeled references that all exist in the bundle — "references/search.md", "references/wiring-blocks.md", "references/wiring-components.md", "references/install-locations.md", and a Contributing section pointing at "references/contributing.md", "references/templates.md", "references/component-quality-bar.md" (each verified present in ./references/). References are one level deep, never nested, and each pointer states its topic. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

5 / 5

Total

19

/

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 excellent description: it states precisely what the skill provides (450 editable blocks/components across many named categories), how they arrive (installed as editable source), and when to reach for it via an explicit 'Use it before...' clause with concrete effect-name triggers and command names. The only weakness is the slightly over-broad 'any named visual ... a chart' trigger, which creates minor overlap risk with generic chart or visual-effect skills.

DimensionReasoningScore

Specificity

Quotes: "About 450 ready-made HyperFrames blocks and components installed as editable source", "transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves", "also for hyperframes add and catalog". The description comprehensively enumerates the content categories, the concrete mechanism (installed as editable source), and the concrete commands (add, catalog), matching the anchor 'Lists multiple specific concrete actions; comprehensive coverage'. It exceeds anchor 4 because coverage of what the registry contains and how it is used is essentially complete for a description, not just 'several actions with minor gaps'.

5 / 5

Completeness

The 'what' is explicit: "About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles...". The 'when' is equally explicit with concrete triggers: "Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog". This directly matches anchor 5, which requires both what and when with concrete trigger phrases; anchor 4 ('when could be more explicit') clearly undersells the explicit 'Use it before...' clause.

5 / 5

Trigger Term Quality

Quotes: "CRT scanlines, glitch, film grain, a chart", "transitions, overlays, titles, kinetic type, captions", "hyperframes add and catalog". These are exactly the natural phrases a user would say when needing this skill, including concrete effect-name synonyms, category terms, and command names. It fits anchor 5 ('comprehensive coverage of natural terms including synonyms'); it is above anchor 4 because no commonly used variation in this domain is conspicuously absent.

5 / 5

Distinctiveness Conflict Risk

Quotes: "Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart)". The HyperFrames-specific vocabulary and named effects (CRT scanlines, glitch, film grain) give it a clear, mostly distinct niche, but the trigger "any named visual ... a chart" is broad and could overlap with general chart/visualization or video-effect skills in the same environment. This lands at anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than 5, whose example has tightly scoped triggers with minimal conflict risk.

4 / 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/hyperframes-registry/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.