general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/general-video/SKILL.md

Quality

Content

73%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, highly actionable workflow with clear sequencing, validation gates, and a completion checklist; progressive disclosure is handled through well-signaled one-level references and a real bundled script. The main drag is conciseness — several preachy passages and the sheer length inflate the token budget without adding executable value.

Suggestions

Tighten the companion-flow prose: replace the rhetorical 'Arrive as the director, not the contractor...' and 'The ceiling belongs to the concept, not the toolbox...' sentences with direct imperatives that state the same rule in one line.

Condense the §5 step-1 catalog-search paragraph and the dispatch economics parenthetical into a short rule plus the command; the measured timing ('5 short scenes ≈ 9 min inline vs ≈ 21 min packetized') is useful but can be a one-line aside rather than a full sentence.

Consider moving the §4 mandatory-reads table and the §6 gates into a short reference file linked from the body, leaving SKILL.md as a leaner overview — this would improve both conciseness and progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly information-dense and avoids explaining basics Claude already knows, but it carries rhetorical/preachy passages ('Arrive as the director, not the contractor...', 'The ceiling belongs to the concept, not the toolbox...') and a long overall footprint that could be tightened.	3 / 5
Actionability	Numerous concrete, executable commands with real flags ('npx hyperframes init "videos/<project>" --non-interactive --example=blank --skill=general-video', 'node <SKILL_DIR>/scripts/frame-packets.mjs --project ...', 'npx hyperframes check') plus specific data-attribute guidance; minor gaps come from placeholder tokens and reliance on loading other skills' references.	4 / 5
Workflow Clarity	A clear 8-step sequenced build (§5), a first-match state-machine table (§2), explicit validation gates ('npx hyperframes lint' for fast feedback, 'npx hyperframes check' as the final gate), and a comprehensive done-checklist (§7) satisfy the explicit-validation, feedback-loop, and checklist criteria.	5 / 5
Progressive Disclosure	References are clearly signaled with one-level-deep '→' notation to other skills' reference files, and the bundled scripts/frame-packets.mjs referenced in the body is present; the overview itself is long and inlines some tables and philosophy that could arguably live separately, keeping it just below the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

82%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: it states a concrete capability, gives explicit when-to-use triggers with named video formats, and proactively disambiguates from sibling skills. Its only weakness is action breadth — 'author or edit' is the sole verb pair, with the remainder being use-case enumeration rather than distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('custom HyperFrames composition') and 1-2 concrete actions ('Author or edit'), but does not enumerate a comprehensive set of distinct actions — the rest of the description lists use cases rather than capabilities.	3 / 5
Completeness	Explicitly answers both what ('Author or edit a custom HyperFrames composition') and when with concrete trigger phrases ('when no specialized workflow fits, or when BRIEF.md sets flow: companion', 'Use for longer or multi-scene pieces...').	5 / 5
Trigger Term Quality	Strong natural-term coverage ('brand and sizzle reels', 'montages', 'static loops', 'static title cards', 'footage remixes', 'freeform builds') that users would plausibly say; a few common synonyms or extensions are absent, keeping it just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche and actively routes overlapping cases away ('Use motion-graphics instead for a short unnarrated motion-first unit', 'Route fresh creation through hyperframes before using this skill'), minimizing wrong-skill triggering.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 15 missing	Warning

	Total	15 / 16 Passed

Repository: heygen-com/hyperframes
Path: skills/general-video/SKILL.md
Commit: 0f8eb89

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.