CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-product-ad-cinematic

Cinematic 5–10s product ad from a product photo + brand brief.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./library/motion/product-ad-cinematic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The body is an efficient, actionable two-phase workflow with a well-designed user-pick checkpoint, cost awareness, and a fallback path, and it correctly keeps cost-heavy steps behind an explicit confirmation. Its weaknesses are minor: a touch of duplication, direction-only prompt guidance for the variant phase, and no intermediate-output validation.

DimensionReasoningScore

Conciseness

The body is lean and imperative ('4 separate `muapi image generate` nodes (model=nano-banana-2, aspect_ratio=16:9 by default)'), with no explanation of concepts Claude already knows. Minor trimmable padding remains: the description is restated verbatim in bold under the H1, and there are two separate 'Notes' sections, so this fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean anchor 5.

4 / 5

Actionability

Guidance is largely executable: exact model IDs (`kling-v3.0-standard-image-to-video`), parameters (`operation=upscale`, `kind=music`, `duration={{duration_sec}}`), output chaining (`$nX.url`), auth setup, and a curl fallback with headers. Small gaps keep it at anchor 4 rather than 5: hero-variant prompts are described directionally ('Vary lighting, palette, framing, and lens') without an example prompt, and node wiring is implied rather than shown.

4 / 5

Workflow Clarity

The two-phase sequence is clear with an explicit human checkpoint ('end your turn... asking the user which one to take forward... Wait') and a failure feedback loop ('If video gen fails after failover, fall back to a still-frame slideshow'). It falls short of anchor 5 only on validation of intermediate results — e.g., no check that the upscale succeeded before animating, and no verification that outputs meet the 5–10s/duration constraint.

4 / 5

Progressive Disclosure

As a single-file skill with no bundle files, it is appropriately self-contained and well-sectioned (Inputs table, phased Steps, Notes, Trigger Keywords) with no nested references. Minor organization gaps — the Trigger Keywords section belongs in the description, and the duplicated description line and split Notes sections slightly muddy navigation — hold it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

53%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.

The description is concise and specific about the deliverable and inputs, but it is what-only: it lacks any 'use when' trigger guidance and omits the synonyms ('commercial', 'product video') that the skill body itself identifies. It reads as a truncated version of a good description.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user wants a product commercial, promo video, or cinematic product video from a product photo.'

Move the trigger keywords already listed in the body ('commercial', 'cinematic ad', 'product video') into the description so they surface at trigger time.

Name the key actions (generate hero-frame variants, upscale, animate, add music) instead of only the end deliverable, so the description reflects the skill's actual capabilities.

DimensionReasoningScore

Specificity

The description names a concrete deliverable ('Cinematic 5–10s product ad') with concrete inputs ('product photo + brand brief'), but lists only this single action — the skill's actual capabilities (hero-frame variant generation, upscaling, image-to-video animation, music) are absent, matching 'names domain and 1-2 concrete actions, but not comprehensive' rather than 'lists several specific actions'.

3 / 5

Completeness

The 'what' is clear and concrete (creates a 5–10s cinematic product ad from a photo and brief), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'product ad', 'product photo', and 'brand brief' are natural and relevant, but common variations users would say — 'commercial', 'promo video', 'product video' — are missing from the description (ironically the body's Trigger Keywords section lists them), matching 'some relevant keywords but missing common variations or synonyms' rather than 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'Cinematic 5–10s product ad from a product photo + brand brief' carves out a narrow, distinctive niche with minimal overlap risk, but without explicit trigger guidance in the description itself it sits slightly below anchor 5's 'clear niche with distinct triggers'.

4 / 5

Total

13

/

20

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.

Validation — 15 / 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

SamurAIGPT/Generative-Media-Skills

Path

library/motion/product-ad-cinematic/SKILL.md

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.