CtrlK
BlogDocsLog inGet started
Tessl Logo

render-brand-identity-reveal

Render a 'brand identity reveal' video from a config — a single poster frame in a real, softly-lit space (real wall, soft-focus plant in the corner, dappled leaf shadow, illuminated poster) whose artwork HARD-CUTS through ~10 on-brand poster mockups (hero product, IG post, hanging banners, sticker sheet, logo lockup, poster, two lifestyle stills, packaging, big icon) then holds on a brand end card. The environment plate is one create-image-fal generation; the mockups are real-DOM HTML frame-stepped via Playwright, perspective-composited into the detected frame quad with the plate's real leaf-shadow multiplied back onto each poster (reads as behind glass), sequenced by FFmpeg. Deterministic assembly, FREE (the plate comes from create-image-fal, the bed from create-music-elevenlabs), music bed only and approved brand copy only. Use for the brand-identity-reveal format.

74

Quality

92%

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

100%

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, and well-structured, with an executable workflow, a verification checkpoint, error-recovery failure modes, and correctly signaled one-level-deep references to real bundle files. It assumes Claude's competence throughout and adds only non-obvious operational detail.

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding explaining what FFmpeg/Playwright/perspective-compositing are, assuming Claude's competence; the few repeated mentions of the shadow-multiply trick reinforce distinct failure modes rather than restate the same point. Not a 2 because there is no unnecessary concept explanation or filler to trim.

3 / 3

Actionability

Provides a copy-paste-ready bash workflow with real script paths and concrete parameters (0.72/0.13 crop, dsf 2, shadow_strength ~0.85, 13.05/1.0), plus specific failure-mode fixes. Not a 2 because the guidance is fully executable rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

The 'Workflow (free assembly)' is a clear ordered command sequence with an explicit verify step ('watch the master — music-only, every poster legible, shadow falls across the art, end card holds') and a Failure Modes section giving error-recovery loops. Not a 2 because the batch/render operation includes both a verification checkpoint and recovery guidance, clearing the validation cap.

3 / 3

Progressive Disclosure

The body is a well-organized overview (Three layers, Inputs, Workflow, Rules, Failure Modes) with one-level-deep, clearly signaled references to verified bundle files (scripts/PIPELINE.md, scripts/config.example.json, scripts/scene.html). Not a 2 because content is appropriately split and navigation is explicit, not a monolithic wall of text.

3 / 3

Total

12

/

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 and distinctive with a clear third-person action list and an explicit trigger, but its trigger terms over-rely on the internal format name and paid-capability identifiers rather than natural user phrasing. Strongest on specificity and distinctiveness, weakest on trigger-term quality.

Suggestions

Broaden the 'Use for...' clause with natural user phrasing, e.g. 'Use when the user wants a brand reveal video, a poster-mockup reel, or a product/identity reveal in a real lit space.'

Move or soften the internal capability identifiers (create-image-fal, create-music-elevenlabs) out of the trigger area so the description reads as user-facing rather than pipeline-internal.

Add 1-2 common keyword variations (e.g. 'brand reveal', 'mockup video', 'identity reveal') to improve natural trigger coverage.

DimensionReasoningScore

Specificity

Lists many concrete actions (render video from a config, hard-cut through ~10 named poster mockup types, perspective-composite into the detected frame quad, multiply leaf-shadow back, sequence via FFmpeg) in third-person voice. Not a 2 because the action set is comprehensive and specific, not just a domain plus a few actions.

3 / 3

Completeness

Clearly states what the skill does and includes an explicit 'Use for the brand-identity-reveal format' trigger, answering both what and when. A weak 3: the trigger is explicit but narrow and self-referential rather than covering multiple natural user cues, which keeps it from being a strong example.

3 / 3

Trigger Term Quality

Trigger phrasing ('Use for the brand-identity-reveal format') and terms lean on an internal format name plus capability identifiers (create-image-fal, create-music-elevenlabs) rather than the natural variations a user would say. Not a 3 because common natural keywords ('brand reveal video', 'product mockup reel') are absent; not a 1 because 'brand identity reveal', 'poster mockups', 'video' are relevant.

2 / 3

Distinctiveness Conflict Risk

The hard-cut poster-mockup-in-a-real-lit-space format with FFmpeg/Playwright composite is a distinct niche unlikely to trigger for unrelated skills. Not a 2 because the format signature is highly specific rather than a broad 'works with videos' overlap.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.