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

70%

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

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with clear progressive disclosure to real bundle files, but the workflow lacks an explicit validation checkpoint and the ffmpeg guidance remains partly placeholder rather than a complete executable pipeline.

Suggestions

Add an explicit verification step (e.g., probe the muxed master with ffprobe to confirm 1080×1920 h264+aac and ~16.6s duration) before declaring success.

Provide a complete end-to-end ffmpeg pipeline script (or reference one in scripts/) so the assembly is copy-paste runnable rather than leaving per-plate hold placeholders inline.

Dimension	Reasoning	Score
Conciseness	Lean contract-style body that assumes Claude's competence — no filler explaining basic concepts, and every line earns its place.	3 / 3
Actionability	Gives concrete ffmpeg commands and specific parameters (1080×1920 @30fps crf18, volume ≈0.4), but stops short of a complete copy-paste pipeline, leaving placeholders like <pose_hold_ms> instead of a fully executable script.	2 / 3
Workflow Clarity	The loop-encode → concat-demux → end-card render → music mux sequence is clearly laid out, but there is no explicit validate/verify checkpoint, which caps workflow clarity at 2 for a batch-assembly operation.	2 / 3
Progressive Disclosure	Overview points to one-level-deep, well-signaled references (scripts/config.example.json, scripts/PIPELINE.md, scripts/README.md), all of which exist as real bundle files.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 distinguishes this capability, but it over-relies on technical jargon for triggers and only implies when to use it rather than stating an explicit 'Use when' clause.

Suggestions

Add an explicit 'Use when…' clause naming natural user phrases (e.g., 'Use when the user asks for a stop-motion cosmetic swatch ad or a hand-swatch-cycle product demo').

Soften jargon-only triggers by pairing technical terms (loop-encode, concat-demux, mux) with plain-language equivalents users would actually say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (PNG→mp4 loop-encode, concat-demux with hard cuts, Playwright HTML end-card render, music mux) rather than vague language.	3 / 3
Completeness	The 'what' is thoroughly specified, but the trigger is only an implied format label ('Use for the stopmotion-hand-swatch-cycle format') with no explicit 'Use when…' clause, capping completeness at 2.	2 / 3
Trigger Term Quality	Contains some relevant terms (stop-motion, product-demo ad, music track, end card) but leans on technical jargon (loop-encode, concat-demux, mux) and lacks common natural variations a user would say.	2 / 3
Distinctiveness Conflict Risk	Describes a very specific niche (stop-motion hand-swatch-cycle ad assembly) with distinct triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 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: 8866b2a

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