CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hyperframes-creative

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

Quality

85%

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

75%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 well-structured router skill: lean, mostly executable, with a clear workflow and one-level-deep references that almost all resolve. The main gaps are the two nonexistent bundle paths (frame-presets/, palettes/*.md), a verification step that lives in the routing table rather than the workflow, and missing example invocations for two of the three scripts.

Suggestions

Fix the dangling routing targets: either create the 'frame-presets/' directory and 'palettes/*.md' files the routing table and workflow point to, or remove/qualify those rows so every route resolves to a real file in the bundle.

Add example invocations for 'scripts/contrast-report.mjs' (e.g., the command with a rendered-frames path) alongside the existing extract-audio-data.py example, since the Scripts section currently shows usage for only one of three scripts.

Fold the post-authoring verification step into the numbered Workflow (e.g., a step 5 pointing to 'references/design-adherence.md') so the validation checkpoint is part of the sequence rather than only a routing-table row.

DimensionReasoningScore

Conciseness

The body is a lean ~68-line router: workflows, a routing table of pointers, and one runnable command, with no concept explanations Claude already knows. The blockquote callout repeats its point ('Read these two FIRST... They are not optional rows in the routing table below... open both before you choose colors or write HTML') and could be tightened, which is a minor over-explanation instance matching the 4 anchor rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Guidance is concrete and executable: exact reference paths per topic, a design-spec precedence chain ('frame.md → design.md → DESIGN.md'), and a copy-paste command ('python skills/hyperframes-creative/scripts/extract-audio-data.py <audio-file>'). Only one of the three listed scripts gets an example invocation (contrast-report.mjs and package-loader.mjs do not), leaving minor gaps that keep it below fully-copy-paste-ready 5.

4 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced (read design spec first → choose route → plan beats → motion guardrails) and a verification checkpoint exists via the 'Post-authoring spec verification' routing row to design-adherence.md, but that validation step is not integrated into the numbered workflow itself. This matches 'clear sequence with most checkpoints present; minor validation gaps' at 4; the operation is not destructive or batch, so no lower cap applies.

4 / 5

Progressive Disclosure

Excellent one-level-deep structure: a routing table with 14 clearly signaled references, all of which resolve to real files in references/, plus a scripts section. Two routing targets — 'frame-presets/' and 'palettes/*.md' — do not exist anywhere in the bundle, which are minor dangling-pointer organization gaps that keep it below the clean 5 anchor.

4 / 5

Total

16

/

20

Passed

Description

87%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 with an explicit 'Use for...' trigger list, concrete file tokens, and a crisp boundary to the sibling animation skill. It is topic-named rather than action-verb-driven and lacks a few common synonyms, which keeps specificity and trigger-term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several specific capability areas with concrete file tokens — 'design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions' — but is topic-driven rather than action-driven (only 'handling', 'planning', 'decisions' as verbs), so it falls just short of the comprehensive concrete-actions anchor at 5 and clearly above the 1-2-actions anchor at 3.

4 / 5

Completeness

Explicitly answers both what ('Non-animation creative direction for HyperFrames videos') and when ('Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-term coverage — 'design spec', 'palettes', 'typography', 'narration', 'beat planning', 'audio-reactive', 'brand / style', plus concrete file names 'frame.md' and 'design.md' — but misses common synonyms a user might say, such as 'colors', 'script writing', or 'voiceover', so it is above the midpoint without full synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche ('Non-animation creative direction for HyperFrames videos') with distinct triggers and an explicit boundary clause — 'For atomic motion patterns and scene blueprints, use `hyperframes-animation`' — minimizing conflict risk with sibling skills.

5 / 5

Total

18

/

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

calesthio/OpenMontage

Path

.agents/skills/hyperframes-creative/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.