CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

captions-overlay

Overlay doctrine for captions in HyperFrames videos — the caption MODEL (drop / rail / embed) and the rule that captions are an OVERLAY composited on top of the film, never a reserved bottom band you shift content up to avoid. Load when adding captions/subtitles to a talking-head or launch video, when deciding whether a phrase should be dropped, ride the verbatim rail, or be promoted to a scarce embedded climax, when laying out a composition that will carry captions (do NOT reserve a keep-out band), or when centering a composition on the true frame center under captions. Applies ON TOP of the `/hyperframes` skill's references/captions.md.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/captions-overlay/SKILL.md

The canonical home for this skill is captions-overlay in heygen-com/hyperframes

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 delivers unusually concrete design doctrine — a classification table, exact geometry values, scarcity thresholds, and a clear validation stance — organized into clean sections that properly position the skill on top of its upstream reference. Its one real weakness is redundancy: the overlay law is restated four times across the intro, its section, the rationale section, and the closing bullets.

Suggestions

State the overlay law once in its own section and cut the restatements — the intro paragraph and "Why these two rules are one doctrine" both re-explain it; keep only the non-redundant point that rail (in front) and embed (behind subject) are both layers added to untouched footage.

Merge the four closing bullets ("Keep the full frame... Reserve nothing") into "The overlay law" as a compact summary checklist instead of a separate section, eliminating the fourth repetition.

Give the embed treatment one line of concrete placement guidance (or an explicit pointer to the upstream captions.md section covering matte occlusion / entrance-exit), since it is currently named but never specified.

DimensionReasoningScore

Conciseness

The body is dense with real rules (no generic padding Claude already knows), but the overlay law is stated four times: in the intro ("a caption line is composited ON TOP of the film... NOT a reserved zone"), again in "The overlay law" section, again in "Why these two rules are one doctrine", and a fourth time as the closing bullet list ("Reserve nothing... center on true center"). That is more than the minor trimmable repetition of anchor 4, so anchor 3 (mostly efficient but could be tightened) is the best fit.

3 / 5

Actionability

Concrete, executable decision guidance throughout: a drop/rail/embed classification table, hard numbers ("y = H / 2 (landscape 540, portrait 960)", "bottom ~5-8% of canvas height", "bottom ~80px center span"), and crisp thresholds ("≤1 embed per beat, never two adjacent/co-visible, ≥ a beat apart"). Not anchor 5 because embed execution details (matte occlusion, "designed entrance + exit") are named but not specified — they are deferred to the upstream skill without a pointer to where.

4 / 5

Workflow Clarity

The decision rules are unambiguous with explicit if/then coverage ("When captions are disabled: identical positioning freedom"; the pure-cinematic exception "use it only for pure-cinematic asks") and an explicit validation stance ("Snapshot review judges caption-over-content legibility visually" in place of the retired keep-out gate). Not anchor 5 because the overall process — classify phrases, lay out at true center, then visually review legibility — is never sequenced; it must be assembled from separate sections.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized sections (caption model, load-bearing rules, overlay law, rationale) and no nested or buried references. It clearly signals its one-level-deep relationship to the upstream file up front ("supplements the upstream `/hyperframes` skill's `references/captions.md`"), and nothing inlined here clearly belongs in a separate file, which fits the simple-skill guidance that a self-contained, well-sectioned skill can score 5.

5 / 5

Total

16

/

20

Passed

Description

83%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 dual doctrine, includes an explicit "Load when" clause with several realistic trigger scenarios, and clearly delimits its relationship to the upstream skill. The main residual risks are trigger overlap with the upstream /hyperframes skill and a few missing caption-synonym variations.

DimensionReasoningScore

Specificity

The description names several concrete capabilities — "the caption MODEL (drop / rail / embed)", captions as "an OVERLAY composited on top of the film, never a reserved bottom band you shift content up to avoid", and "centering a composition on the true frame center" — rather than vague domain labels. It falls short of anchor 5 because it is a doctrine statement rather than a comprehensive inventory of executable actions.

4 / 5

Completeness

Both questions are answered explicitly: the "what" ("Overlay doctrine for captions in HyperFrames videos — the caption MODEL (drop / rail / embed) and the rule that captions are an OVERLAY composited on top of the film") and the "when" via a concrete "Load when adding captions/subtitles... or when centering a composition on the true frame center under captions" clause with multiple trigger scenarios. This matches the anchor-5 example structure of explicit what + explicit when with concrete triggers.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "adding captions/subtitles to a talking-head or launch video", "dropped, ride the verbatim rail, or be promoted to a scarce embedded climax", and "frame center under captions". Not anchor 5 because common variations like "text on screen", "lower third", or "burned-in captions" are missing, but coverage goes beyond anchor 3's partial keyword set.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (captions in HyperFrames videos) and explicitly self-positions ("Applies ON TOP of the `/hyperframes` skill's references/captions.md"), so it is mostly distinct. It is not anchor 5 because its triggers ("adding captions/subtitles to a talking-head or launch video") overlap with the upstream /hyperframes skill itself, so two skills can plausibly fire on the same request.

4 / 5

Total

17

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

heygen-com/hyperframes

Path

.claude/skills/captions-overlay/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.