CtrlK
BlogDocsLog inGet started
Tessl Logo

muapi-jewelry-product-video

Create a luxury jewelry advertisement with high-end commercial cinematography and detailed macro animation.

54

Quality

61%

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

Quality

Content

87%

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, highly actionable, and well-structured for a single-purpose recipe, with concrete models, commands, and prompt templates. Its main weakness is the absence of an explicit error-recovery or validation loop for the generation and polling operations.

Suggestions

Add a short feedback loop for failed or low-quality generations (e.g., check muapi predict result status; if failed, retry with adjusted prompt before proceeding) to lift workflow clarity above 2.

State the expected output of each phase explicitly (e.g., an image artifact in Phase A, two video clips in Phase B) so validation of each step's result is unambiguous.

Clarify the ffmpeg concat step from the note into an explicit numbered step with the actual command, since merging the shots is part of the final deliverable.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a compact inputs table, specific numbered prompts, and brief notes — and it assumes Claude's competence without explaining what models or cinematography are, so most tokens earn their place.

3 / 3

Actionability

It provides concrete, executable guidance: named models (e.g. 'nano-banana-2-edit', 'grok-imagine-image-to-video'), specific CLI commands ('muapi image generate', 'muapi video from-image'), full prompt templates with placeholders, and a copy-paste-ready curl fallback with polling, making it fully actionable.

3 / 3

Workflow Clarity

The two-phase sequence is clearly numbered and includes an explicit approval checkpoint before Phase B, but for generation/polling operations there is no validation or feedback loop describing what to do if generation fails or quality is poor, capping workflow clarity at 2 per the batch/risky-operation rule.

2 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external bundle files, and it is well-organized into clear sections (Inputs, Steps, Trigger Keywords, Notes), so per the simple-skill scoring note progressive disclosure earns a 3.

3 / 3

Total

11

/

12

Passed

Description

35%

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 conveys the skill's purpose and aesthetic scope concisely, but it lacks any trigger guidance and contains no natural keywords a user would actually say. Adding a 'Use when...' clause with user-voiced trigger terms would raise completeness, trigger quality, and distinctiveness together.

Suggestions

Append an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants a jewelry product video, luxury ad, or diamond/ring commercial animation.'

Include natural trigger terms users would actually say (e.g. 'jewelry video', 'diamond animation', 'ring commercial') directly in the description rather than only in the body's Trigger Keywords section.

Briefly enumerate the concrete actions (generate base image, animate macro shots, merge into a short commercial) so the capability list reads as comprehensive rather than a single stylistic sentence.

DimensionReasoningScore

Specificity

The description names the domain ('luxury jewelry advertisement') and some specific style attributes ('high-end commercial cinematography', 'detailed macro animation'), but does not enumerate the multiple concrete actions the skill performs (image generation, video animation, shot merging), so it is not comprehensive enough for a 3.

2 / 3

Completeness

It clearly states what the skill does ('Create a luxury jewelry advertisement...') but provides no 'when should Claude use it' guidance, so per the missing-'Use when...' rule completeness is capped at 2.

2 / 3

Trigger Term Quality

The description contains no natural trigger keywords a user would say; phrases like 'high-end commercial cinematography' and 'detailed macro animation' are technical descriptor language rather than user-voiced terms, and no 'Use when...' clause is present.

1 / 3

Distinctiveness Conflict Risk

The luxury jewelry/video-ad niche is reasonably specific, but the description lacks distinct trigger phrasing that would make it unambiguously distinguishable from other video-generation skills, leaving it in the 'somewhat specific but could overlap' band rather than a clear 3.

2 / 3

Total

7

/

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
SamurAIGPT/Generative-Media-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.