CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wireframe-portal-title

A wireframe portal bursts open, the title comes through, then its letters swap into a second phrase. HyperFrames block, 1920×1080, 8s, 9 variables.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./registry/blocks/wireframe-portal-title/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a tight, executable reference: complete install/mount/render commands, a fully specified variable table, an explicit runtime contract, and hard-won editing rules stated as constraints rather than explanations. The only deductions are scattered pinned version numbers, a missing post-install verification step, and structure that is solid but not exceptionally split. All listed bundle files check out against the actual assets directory.

DimensionReasoningScore

Conciseness

The body is lean and dense with information Claude would not already know (composition id, variable ranges, runtime contract, editing rules) — nothing explains known concepts. Not a 5 because pinned version numbers (hyperframes@0.8.12, three.js 0.181.2, GSAP 3.14.2) are time-sensitive information scattered inline rather than isolated, which the guidelines say penalizes conciseness.

4 / 5

Actionability

Everything is copy-paste executable: the install command 'npx hyperframes add wireframe-portal-title', a complete mount <div> with all data attributes, a full render command with example --variables JSON, and a variable table with types, defaults, and step ranges. Not below 5 because no key execution detail is missing.

5 / 5

Workflow Clarity

The install → mount → render sequence is clearly ordered, with numbered editing rules and a seek-safety contract. Not a 5 because there is no validation checkpoint (e.g. verifying the block mounted or the timeline registered) after install/mount; not 3 because the operations are non-destructive single-purpose renders, so validation gaps are minor rather than missing.

4 / 5

Progressive Disclosure

Structure is good: a Files section accurately listing the bundled assets (the three Geist TTFs and OFL license all exist under assets/fonts/), sections for Install/Variables/Runtime contract/Editing rules, and one-level references with no nesting. Not a 5 because the skill runs slightly over the under-50-line simple-skill threshold and the large 63 KB composition HTML carries all implementation detail in a single inline-referenced file, which is appropriate here but leaves organization gains on the table.

4 / 5

Total

17

/

20

Passed

Description

58%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 paints a concrete, distinctive picture of the composition but functions purely as a 'what' statement. It lacks any 'use when' trigger guidance (capping completeness at 3) and omits natural synonyms like 'animation' or 'title reveal' that users would actually say. Third person voice is used correctly and there is no fluff.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating an animated title intro, wireframe text reveal, or portal-style opening sequence in HyperFrames.'

Include natural synonyms and format hints users would say: 'title animation', 'text reveal', 'letter swap', alongside the existing terminology.

State the capability in operator terms (e.g. 'Renders a 1920×1080 animated title...') so it reads as a skill capability, not just a scene description.

DimensionReasoningScore

Specificity

The description lists several concrete visual actions — 'a wireframe portal bursts open', 'the title comes through', 'its letters swap into a second phrase' — plus concrete format facts (1920×1080, 8s, 9 variables). Falls just short of the 5 anchor because it describes the artifact's behavior rather than enumerating the skill's full capability set.

4 / 5

Completeness

The 'what' is clear and vivid (portal burst title sequence that swaps into a replacement phrase), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent, not even weakly implied; not 2 because the 'what' is concrete.

3 / 5

Trigger Term Quality

Relevant keywords exist ('wireframe', 'portal', 'title', 'letters swap', 'phrase', 'HyperFrames block'), but common natural variations users might say ('text animation', 'title reveal', 'intro animation') are missing, and 'HyperFrames block' is niche jargon. Matches the 'some relevant keywords but missing common variations' anchor; not 4 because synonym coverage is thin.

3 / 5

Distinctiveness Conflict Risk

The niche is distinctive — a wireframe portal title with letter-swap specific to HyperFrames — so conflict risk is low. Not a 5 because 'title' and 'portal' are words that could appear in other title/animation contexts, and no trigger phrase anchors the distinction.

4 / 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: 7 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

heygen-com/hyperframes

Path

registry/blocks/wireframe-portal-title/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.