CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-jewelry-product-video

Create a luxury jewelry advertisement with high-end commercial cinematography and detailed macro 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/jewelry-product-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 a tight, well-structured two-phase workflow with concrete commands, model IDs, and ready-to-use prompts, plus an explicit user-approval checkpoint. Main weaknesses are the never-shown merge command, the typo-like duplicated alternative in Phase B step 2, and the absence of explicit output validation between generation and final delivery.

Suggestions

Replace the Phase B step 2 duplication ('muapi video from-image or muapi video from-image') with the single intended command, and give the exact ffmpeg concat command (or a script reference) so the merge step is executable rather than a parenthetical note.

Add an explicit validation checkpoint between generation and presentation, e.g. 'Verify each video completed via muapi predict result before concatenating, and re-submit failed generations' — this also strengthens the feedback loop for the batch-like two-shot workflow.

Show one complete CLI invocation (with argument syntax) for muapi image generate and muapi video from-image so the commands are copy-paste ready rather than implied.

DimensionReasoningScore

Conciseness

The body is lean — an inputs table, phased steps with literal prompt text, and terse agent notes; it does not explain concepts Claude already knows. Minor trimmable padding exists (the 'Trigger Keywords' section largely duplicates the description's job, and the final Notes repeat fallback mechanics). Efficient with minor over-explanation — anchor 4, just short of the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Concrete guidance throughout: specific CLI commands with model IDs ('muapi image generate' model='nano-banana-2-edit', 'grok-imagine-image-to-video'), full ready-to-use prompts, and a curl fallback for unaliased endpoints. Gaps: full CLI invocation syntax is never shown, the ffmpeg merge is only a parenthetical 'You can use... ffmpeg concat' with no command, and Phase B step 2 reads 'muapi video from-image or muapi video from-image' — a duplicated non-alternative. Mostly executable with minor gaps — anchor 4, not 5.

4 / 5

Workflow Clarity

Clear sequence: Phase A image generation, an explicit user-approval checkpoint ('Present the luxury image to the user for approval'), Phase B's two timestamped sequential shots, then merging and final presentation. Not 5 because output validation is implicit — there is no step to confirm each generation succeeded or verify the concatenated result before presenting, and the merge step is framed as optional.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories) and the body is self-contained with well-organized sections (Inputs, Steps with Phase A/B, Trigger Keywords, Notes) and no nested references. Per the simple-skill guidance, a short single-purpose skill with no need for external references scores 5 with just well-organized sections, which this has.

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 clearly and concisely states what the skill does within a distinctive niche, but it omits any 'Use when...' trigger guidance, which both caps completeness and limits trigger-term quality. Adding an explicit trigger clause with natural user phrasings would lift two dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for a jewelry or luxury product video, a ring commercial, or a high-end product ad combining still imagery and macro animation.'

Broaden trigger-term coverage with natural synonyms users would actually say, such as 'jewelry ad', 'product commercial', 'diamond/ring video', or 'luxury product showcase'.

State the full capability scope in the 'what' — e.g. that the skill generates a luxury still image and then animates it into a short commercial — so specificity moves from 1-2 actions to comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ('luxury jewelry advertisement') and 1-2 concrete actions ('high-end commercial cinematography and detailed macro animation'), but does not comprehensively cover the skill's capabilities (image generation, video assembly). It matches anchor 3: domain plus a couple of concrete actions, not the several specific actions of anchor 4.

3 / 5

Completeness

The 'what' is clear ('Create a luxury jewelry advertisement with high-end commercial cinematography and detailed macro animation'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not 4 because the 'when' is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

'luxury jewelry advertisement', 'commercial cinematography', and 'macro animation' are relevant on-domain terms, but common user phrasings like 'jewelry ad', 'product video', 'ring', or 'commercial' as a synonym are absent. Some relevant keywords without common variations — anchor 3, not the synonym-level coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The luxury-jewelry-advertising niche is fairly distinct with domain-specific terms, minimizing conflict with unrelated skills, but the absence of any mention of video generation, the muapi tool, or the workflow leaves minor overlap risk with generic ad/video-generation skills. Mostly distinct with minor overlap — anchor 4, not the clear-niche-with-distinct-triggers of anchor 5.

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/jewelry-product-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.