CtrlK
BlogDocsLog inGet started
Tessl Logo

compose-creator-layer

Composite a generated creator track into a product layer, per beat — in the creator's zone on split beats (either side of a seam), full frame on creator beats, hidden on product beats — with the creator's voice as the audio (loudness -14 LUFS) and an optional ducked music bed, or a music-only or silent master for voiceless formats. Free, local ffmpeg. Pairs with footage-cutlist (the layer) and create-creator-takes-h3 (the creator). Use for split-screen, screen-insert and any creator-over-product format.

71

Quality

89%

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

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.

A tight, executable single-command skill body: lean on tokens, concrete in its command and rules, and clear about prerequisites and downstream ordering. The small deductions come from the invisible `--audio` option in the usage line, the unpathed script reference, and the absence of an explicit output-validation step.

Suggestions

Add `--audio creator|music|none` to the Run usage line so every option appears in the copy-paste command rather than only in the bullet list.

Invoke the script by its bundle path (e.g. `python scripts/compose.py ...`) so the reference matches the actual file location.

Add a brief validation step — e.g. confirm the compose summary line / output duration before handing off to caption-burn — to close the workflow's missing feedback loop.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and operational — 'The take goes in as generated', '0.30 keeps the head in the upper third' — with no concept explanations, no padding, and every token earning its place.

5 / 5

Actionability

The Run block gives a copy-paste-ready bash command with every flag documented in the bullets, but the `--audio creator|music|none` option never appears in the usage line and the script is invoked as `compose.py` without its bundle path (`scripts/compose.py`), leaving minor gaps.

4 / 5

Workflow Clarity

Prerequisites and ordering are explicit ('re-render it after align_beats.py', '--draft layers are refused', 'Captions come after this'), but there is no written validation checkpoint for confirming the render succeeded or an error-recovery loop before handing off to caption-burn.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized '## Run' and '## Rules' sections and no external references needed, but the one bundle file is referenced without its actual path — the skill says `python compose.py` while the script lives at scripts/compose.py, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

92%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 dense, highly specific description that explicitly covers what the skill does, when to use it, and how it relates to sibling skills. The only minor weakness is trigger-term breadth — a few natural user phrasings for the format are absent.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — compositing per beat with 'creator's zone on split beats (either side of a seam), full frame on creator beats, hidden on product beats', 'loudness -14 LUFS', 'optional ducked music bed', 'music-only or silent master' — giving comprehensive coverage of the skill's behavior.

5 / 5

Completeness

It explicitly answers both what the skill does (detailed per-beat compositing and audio behavior) and when to use it via the concrete 'Use for split-screen, screen-insert and any creator-over-product format' clause.

5 / 5

Trigger Term Quality

'Use for split-screen, screen-insert and any creator-over-product format' provides good natural domain keywords, but common user phrasings such as overlay, picture-in-picture, or talking-head-over-gameplay are missing, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (beat-level creator-over-product compositing) with distinct triggers, plus explicit sibling-skill scoping ('Pairs with footage-cutlist (the layer) and create-creator-takes-h3 (the creator)'), minimizes overlap risk.

5 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.