CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-product-showcase-video

Create a dynamic product showcase with explosive ingredient arrangements, followed by a realistic motion animation.

Quality

72%

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-showcase-video/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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, executable two-phase recipe with exact model IDs, templated prompts, an approval checkpoint between phases, and practical agent notes for auth and API fallback. Its main weaknesses are minor: incomplete CLI invocation syntax (flags and the curl request body are left implicit) and no guidance for recovering from failed or unsatisfactory generations.

DimensionReasoningScore

Conciseness

The body is lean: a compact inputs table, prompt templates that are themselves the payload, and no explanations of concepts Claude already knows. Minor trimmable redundancy (bold restatement of the description under the title and the 'Trigger Keywords' meta-section) keeps it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Concrete commands with exact model IDs ('muapi image edit' model=bytedance-seedream-v4.5-edit, 'muapi video from-image' model=seedance-v1.5-pro-i2v-fast), full prompts, aspect ratios, an auth precondition, and a curl fallback. Minor gaps: the CLI calls don't show flag syntax for passing the reference image and prompt, and the curl fallback contains a literal '{...}' body, so it isn't fully copy-paste ready.

4 / 5

Workflow Clarity

A clear two-phase sequence with an explicit user-approval checkpoint ('Present the generated dynamic image to the user for approval', 'Once the image is approved') and missing-input handling ('If product_image is not provided, ask the user'). It lacks an error-recovery loop for failed or poor-quality generation, which the anchor-5 example requires.

4 / 5

Progressive Disclosure

This is a compact (~50-line), self-contained skill with no external bundle files and no content that belongs in a separate file; sections (Inputs / Steps / Trigger Keywords / Notes) are well organized, which per the simple-skill exception earns the top anchor.

5 / 5

Total

17

/

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 communicates a clear, distinctive capability in third person with concrete output language, but it lacks any explicit 'when to use' trigger guidance and natural trigger phrasing, leaving users and the skill router without usage boundaries. It sits at the midpoint of the rubric: good 'what', missing 'when'.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when the user wants a product ad video, product showcase, or commercial with flying/fresh ingredients' — this would lift both completeness and trigger_term_quality.

Include natural trigger synonyms users actually say (product ad, commercial video, product video, ingredient explosion) directly in the description rather than only in the body's Trigger Keywords section.

Mention the two concrete actions by name (edit the product photo into a dynamic ad image, then animate it into a video) so the 'what' lists several specific actions instead of one composite outcome.

DimensionReasoningScore

Specificity

The description names the domain ("dynamic product showcase") and 1-2 concrete outputs ("explosive ingredient arrangements", "realistic motion animation"), but does not list several specific actions, so it matches the 'names domain and 1-2 concrete actions' anchor rather than the 'lists several specific actions' level above.

3 / 5

Completeness

The 'what' is clear (create a dynamic product showcase image and motion animation), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "product showcase" and "motion animation" are relevant, but common natural variations users would say ("product ad", "commercial video", "product video") are missing from the description, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The combination of "explosive ingredient arrangements" and "realistic motion animation" carves a mostly distinct niche with minor overlap risk against closely related generic video/ad-generation skills; it falls between the 'somewhat specific' and 'clear niche' anchors, noticeably above the midpoint.

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-showcase-video/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.