render-multiworld

Assemble a silent, music-led 3-world product-tour ad — trim and hard-cut-concat the per-world WIDE-arrival + top-down-macro clips, composite the HTML/Playwright brand end card ("FIND YOUR DAILY." + handwritten scent labels + arrows) over an AI flat-lay background, and mux one music bed into a 720x1280 web master. FREE, deterministic assembly (Playwright + PIL/HTML + FFmpeg); the recipe supplies the config and gates the paid clip/background/music calls. Use for the multiworld-product-tour format.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ads/capabilities/render-multiworld/SKILL.md

Quality

Content

68%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-organized, parameter-rich assembler overview with clear sequencing and good progressive disclosure to real bundle files. It is held back by missing explicit validation checkpoints in the batch workflow and some duplication between the body and the scripts bundle.

Suggestions

Add an explicit validation checkpoint in the Run workflow, e.g. after trimming verify each clip is sealed-bottle-clean and matches 720x1280/24fps before concat, with a re-roll path on failure.

Inline at least one complete, copy-paste ffmpeg command (e.g. the trim+re-encode or the loudnorm mux) so the assembly is executable directly from SKILL.md.

De-duplicate the Contract/Gaps material against scripts/README.md and PIPELINE.md so the body stays a true overview and detail lives one level deep.

Dimension	Reasoning	Score
Conciseness	Lean, assumes Claude's competence, and avoids explaining FFmpeg/Playwright basics, but the Contract and Gaps sections restate FREE/silent/sealed-bottle points already covered in Run and in the bundle files — minor trimming available.	4 / 5
Actionability	Run steps give concrete, specific parameters (720x1280, 24fps, yuv420p, loudnorm I=-16:TP=-1.5:LRA=11, AAC 192k, scene order S01→S07) that a competent Claude can execute, though no full copy-paste ffmpeg command lines or scripts are inlined and the real render scripts live outside the bundle.	4 / 5
Workflow Clarity	The four-step Run sequence (Trim → End card → Concat → Music mux) is clearly ordered, but this batch operation over six clips has no explicit validation/verification checkpoint before concat/encode, so the batch-validation cap applies.	3 / 5
Progressive Disclosure	The body is a well-sectioned overview pointing one level deep to real bundle files (scripts/PIPELINE.md, scripts/README.md) clearly signaled at the end; the main gap is content overlap between the body's Run/Contract and the scripts files.	4 / 5
	Total	15 / 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 dense, concrete, third-person description that names specific actions and a distinct format niche. Its main weakness is a single narrow 'Use for...' trigger phrase rather than a richer set of natural trigger terms.

Suggestions

Expand the trigger clause with natural user phrasings and synonyms, e.g. 'Use for the multiworld-product-tour format, 9:16 product-tour ads, or three-world scent tours'.

Add the deliverable format/extension as a trigger term (e.g. '720x1280 web master' / '.mp4') so users naming the output can find it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete assembly actions — 'trim and hard-cut-concat the per-world WIDE-arrival + top-down-macro clips', 'composite the HTML/Playwright brand end card', 'mux one music bed into a 720x1280 web master' — with comprehensive coverage of the pipeline.	5 / 5
Completeness	Clearly states what it does (the full assembly) and includes a 'Use for the multiworld-product-tour format' trigger, but the 'when' is a single terse format name rather than multiple concrete trigger phrases, so it stops short of the anchor-5 example.	4 / 5
Trigger Term Quality	Includes natural terms like 'product-tour ad', 'music bed', 'end card', and the explicit 'multiworld-product-tour format' trigger, but the vocabulary is niche/proprietary with few synonyms or file extensions a user would naturally vary.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche — a silent music-led 3-world 9:16 product-tour assembler at 720x1280 — with triggers unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/ads/capabilities/render-multiworld/SKILL.md
Commit: 2523432

Reviewed: 13 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.