CtrlK
BlogDocsLog inGet started
Tessl Logo

mix-master

Canonical short-form-ad audio mix in one FFmpeg pass. VO loudnorm + 3.0× per-clip + 2.0× mix, music 0.13 base + apad+afade, sidechain compress 20:1 @ 0.01, climax line +20%, optional video-to-music duration sync. Replaces the reactive multi-round tuning that cost v03 6+ passes.

65

Quality

82%

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

88%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 lean, highly actionable with exact FFmpeg chains and a working example, and clearly sequenced with validation and verification checkpoints; progressive disclosure is good with a real referenced script.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — no padding explaining FFmpeg or loudnorm — but the Purpose paragraph's narrative ('round 1 music too loud, round 2 VO too quiet...') is motivational context that could be trimmed; minor instances of over-explanation keep it just below 5.

4 / 5

Actionability

Fully executable: exact filter_complex chain syntax ('loudnorm=I=...:TP=...:LRA=...,adelay=<start>|<start>,volume=<vo_volume>'), a real copy-paste example invocation, and a concrete reference to scripts/mix.sh (which exists) covering the common case.

5 / 5

Workflow Clarity

Clear five-step sequence with explicit validation at step 1 ('--vo and --vo-starts must be same length') and verification at step 5 (ffprobe loudness probe, verification.md pass/fail), plus Quality Checks and Failure Modes covering error recovery — well above the destructive/batch cap of 3.

5 / 5

Progressive Disclosure

Well-organized into labeled sections (Purpose, Inputs, Workflow, Output, Quality Checks, Failure Modes, Example) with a clearly signaled one-level reference to scripts/mix.sh used in the example; minor gaps only — most parameter detail is appropriately inline rather than split into separate files.

4 / 5

Total

18

/

20

Passed

Description

67%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 is highly specific and clearly distinct, but is written for an expert audience in jargon-heavy shorthand and omits any 'Use when...' trigger guidance, capping completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when mixing VO, music, and SFX for a short-form ad in a single FFmpeg pass.'

Soften the parameter-heavy jargon (e.g. 'sidechain compress 20:1 @ 0.01') with plain-language triggers like 'duck music under voiceover' that a user would actually say.

Include common natural terms and file extensions ('mix audio for ads', '.mp4', '.mp3', 'voiceover/music bed mix') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with exact parameters — 'VO loudnorm', '3.0x per-clip + 2.0x mix', 'music 0.13 base + apad+afade', 'sidechain compress 20:1 @ 0.01', 'climax line +20%', 'video-to-music duration sync' — comprehensive coverage of the mix protocol.

5 / 5

Completeness

Has a clear 'what' (canonical short-form-ad audio mix protocol) but no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Contains some relevant keywords ('audio mix', 'FFmpeg') but is dominated by technical jargon ('VO loudnorm', 'apad+afade', 'sidechain compress 20:1 @ 0.01') and misses the natural phrases and synonyms a user would actually say, with no file extensions.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (short-form-ad FFmpeg audio mix with a specific parameterized protocol) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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
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.