render-imessage-cascade

Assemble an iMessage notification-cascade video ad (≈14s, 9:16) from a phone-on-desk plate + 3–5 messages — authentic Apple Messages banners composited in PIL (SF Pro text, green Messages icon, warm translucent-greige fill, soft shadow) spring in one-by-one at the BOTTOM and push the stack UP, a right-aligned Show-less/X pill rides above, the X clears the stack, then a serif end card resolves. FREE assembly (PIL + ffmpeg); the recipe supplies the per-brand plate, notifications, and end-card config and gates the paid plate-clean/music calls to their own capabilities. Use for the imessage-notification-cascade format.

Quality

71%

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-imessage-cascade/SKILL.md

Quality

Content

57%

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

The body is well-structured with verified bundle references and exact spec constants, but it relies on delegate scripts for executable code and presents the pipeline as prose rather than an explicit validated workflow, with some redundancy across sections.

Suggestions

De-duplicate the bottom-up push and SF Pro font details, stating each once in its canonical section.

Add a short copy-paste invocation example (e.g. `python scripts/build_assets.py config.json && python scripts/compose.py ...`) so the body is actionable without opening the scripts.

Render the compose pipeline as an explicit numbered workflow with a validation/QC checkpoint after encode rather than a prose bullet.

Dimension	Reasoning	Score
Conciseness	Mostly dense and load-bearing without explaining basics Claude knows, but the bottom-up push mechanic and the SF Pro font requirement are each restated across the Scripts and Craft rules sections and could be tightened.	2 / 3
Actionability	Provides exact geometry constants and points to real executable scripts, but the body itself contains no inline copy-paste code or commands — it delegates all executable detail to the bundle files.	2 / 3
Workflow Clarity	The compose pipeline is laid out as a clear arrow sequence with a 'watch (QC the final master)' step, but checkpoints are implicit and presented as prose within a script bullet rather than an explicit numbered workflow with feedback loops.	2 / 3
Progressive Disclosure	Well-organized into clear sections with one-level-deep references to real verified bundle files (build_assets.py, compose.py, config.example.json), matching the clear-overview anchor.	3 / 3
	Total	9 / 12 Passed

Description

85%

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 specific, complete, and clearly distinct, with explicit what-and-when guidance and third-person voice. Its main weakness is a narrow single-format trigger clause that could broaden its natural-language coverage.

Suggestions

Add natural-language trigger variations to the 'Use for' clause (e.g., 'iOS notification stack video', 'text-message cascade ad') so users phrasing it differently still match.

Consider naming broader trigger contexts (phone-on-desk ad, iOS Messages notification trend) alongside the format identifier.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'authentic Apple Messages banners composited in PIL', 'spring in one-by-one at the BOTTOM and push the stack UP', 'the X clears the stack', 'serif end card resolves', 'gates the paid plate-clean/music calls' — which matches the comprehensive multi-action anchor.	3 / 3
Completeness	Clearly states what it does and provides an explicit 'Use for the imessage-notification-cascade format' trigger clause, answering both what and when, so it is not capped at 2.	3 / 3
Trigger Term Quality	Includes the niche format name and several relevant terms, but the 'Use for the imessage-notification-cascade format' trigger is a single narrow identifier missing common natural-language variations a user might actually say.	2 / 3
Distinctiveness Conflict Risk	A highly specific niche format with a distinct trigger; the iMessage notification-cascade mechanic is unlikely to overlap with or mis-trigger other skills.	3 / 3
	Total	11 / 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-imessage-cascade/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.