render-stopmotion-hand-swatch-cycle

Assemble a stop-motion hand-swatch-cycle product-demo ad from a config — a sequence of still PLATES (one hand swiping a single-barrel cosmetic across a cream skin-patch, the barrel + swatch changing per plate while the hand, background, crop, and lighting stay locked) is PNG→mp4 loop-encoded at each plate's own stop-motion hold (fast motion frames 150–250ms, per-shade ~380ms, hero beats 1100–1800ms), concat-demuxed with HARD cuts into a silent master, closed on a Playwright HTML-rendered branded end card (serif tagline + sans subtitle + real logo SVG over a hero BG, never AI-rendered text), and muxed with a pre-sourced music track playing under the end card with a fade tail (no VO). This is the FREE deterministic assembly stage (loop-encode + concat-demux + end-card render + music mux); the master-anchor plate, shade plates, and end-card BG come from create-image-gpt-image-fal and the track from create-music-elevenlabs. Use for the stopmotion-hand-swatch-cycle format.

Quality

68%

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/ads/capabilities/render-stopmotion-hand-swatch-cycle/SKILL.md

Quality

Content

61%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 focused, technically concrete contract for a deterministic assembly skill with well-organized one-level-deep bundle references. It is weakened by repeated FREE/$0 framing, no validation checkpoint in the batch workflow, and references that are not formatted as navigable links.

Suggestions

Add an explicit validation checkpoint in the Run/Contract flow (e.g., 'After concat, verify the master duration ≈ sum of holds + 3s end card and that plate count matches the config before muxing music').

Deduplicate the 'FREE/deterministic/$0' message — state it once in the intro and let the Contract focus on the technical rules.

Convert the bundle mentions into a short References section with markdown links (e.g., '[PIPELINE.md](scripts/PIPELINE.md)') for clearer navigation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient technical contract content, but the 'FREE/deterministic/$0' message repeats across the intro, Run, and Contract sections, and the cadence numbers (150–250ms, ~380ms, 1100–1800ms) duplicate the bundled scripts.	3 / 5
Actionability	Provides concrete executable fragments ('ffmpeg -loop 1 -t <pose_hold_ms>', 'ffmpeg -f concat', 1080×1920 @ 30fps crf18, volume ≈0.4, fade in/out) with only minor gaps — the full runnable pipeline is referenced via scripts rather than inlined.	4 / 5
Workflow Clarity	The encode→concat→end-card→mux sequence is clear, but this batch assembly has no explicit validation/verification checkpoint (e.g., verify master duration/playback, check plate count), capping workflow clarity at 3 per the batch-operations rule.	3 / 5
Progressive Disclosure	Real one-level-deep bundle files (scripts/PIPELINE.md, scripts/README.md, scripts/config.example.json — all verified present) are signaled early in prose, but they are plain-text mentions rather than navigational links and lack a dedicated references section.	4 / 5
	Total	14 / 20 Passed

Description

76%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 conveys the full assembly pipeline and an explicit trigger, with strong distinctiveness. Its main weakness is a narrow trigger vocabulary that offers few natural synonyms a user might say.

Suggestions

Add a couple of natural-language trigger variants (e.g., 'Use when assembling a stop-motion swatch-cycle cosmetic demo, a hand-swatch shade-cycle ad, or re-cutting an existing cycle') to broaden trigger_term_quality.

Make the 'when' clause situational rather than only naming the format (e.g., 'Use when you have ordered plate PNGs + holds + an end-card BG + a music track and need the free deterministic master').

Dimension	Reasoning	Score
Specificity	Lists multiple concrete assembly actions — 'PNG→mp4 loop-encoded', 'concat-demuxed with HARD cuts', 'Playwright HTML-rendered branded end card', 'muxed with a pre-sourced music track' — covering the full pipeline comprehensively.	5 / 5
Completeness	Clearly states what the skill does (the full assembly pipeline) and includes an explicit 'Use for...' when-clause, but the when could be more situationally explicit rather than a single format-name trigger.	4 / 5
Trigger Term Quality	The trigger is essentially the format name ('stop-motion hand-swatch-cycle', 'product-demo ad', 'Use for the stopmotion-hand-swatch-cycle format'); relevant but lacking common synonyms or variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	The 'stop-motion hand-swatch-cycle' niche is highly specific with distinct triggers, making conflict with other skills minimal.	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
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-stopmotion-hand-swatch-cycle/SKILL.md
Commit: 2523432

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