muapi-cartoon-dance-animation

Convert a photo of a person into a Pixar-style 3D cartoon character, then animate it using a reference dance or motion video.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./library/motion/cartoon-dance-animation/SKILL.md

Quality

Content

70%

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 well-structured, self-contained two-phase recipe with clear sequencing and an approval checkpoint, but its embedded prompts are redundant and its CLI invocations stop short of fully copy-paste-ready syntax.

Suggestions

Show one fully runnable example invocation (or the complete curl JSON payload) for each phase so the commands are copy-paste ready rather than described in prose.

Tighten the negative prompt by consolidating redundant negations into grouped categories to reduce token cost without losing coverage.

Add a brief failure-recovery note (e.g., what to do if generation errors or a poll times out) to strengthen the workflow's validation/feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is largely free of concept-explaining fluff and the 'Notes for the Executing Agent' are lean, but the embedded generation prompt and especially the negative prompt are highly redundant ('no outfit change, no costume change, no new clothes, no extra accessories, no glasses, no headphones, no makeup...'), so it fits 'mostly efficient but could be tightened' rather than fully lean.	2 / 3
Actionability	It names concrete commands and models ('muapi image edit' model='nano-banana-2-edit', 'muapi video from-image'/'edit_video' model='kling-v2.6-std-motion-control') with full prompt text and a curl fallback, but the actual runnable CLI invocation form (flags/JSON payload) is implied rather than given verbatim, matching the 'some concrete guidance but incomplete; missing key details' anchor.	2 / 3
Workflow Clarity	Phases A and B are clearly sequenced with input-gathering gates and an explicit approval checkpoint ('Present the generated cartoon character to the user for approval') before proceeding, satisfying the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets are empty) and the recipe is self-contained with well-organized sections (Inputs, Steps, Trigger Keywords, Notes); per the simple-skills scoring note this warrants a 3 for clear organization without nested references.	3 / 3
	Total	10 / 12 Passed

Description

67%

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, clearly conveying a concrete two-phase pipeline, but it omits an explicit 'Use when...' trigger clause and only partially covers natural trigger terms, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit 'Use when...' trigger clause to the description (e.g., 'Use when the user wants to cartoonify a photo and animate it into a dance or motion video') so the 'when' is stated, not just implied by the body's Trigger Keywords.

Broaden natural trigger keywords inside the description to include common phrasings like 'animate my photo', 'cartoonify', and 'turn a photo into a dancing 3D character'.

Keep the third-person imperative voice ('Convert...', 'animate...'); it already avoids first/second person and should be preserved.

Dimension	Reasoning	Score
Specificity	Quotes two concrete actions — 'Convert a photo of a person into a Pixar-style 3D cartoon character' and 'animate it using a reference dance or motion video' — naming both transformations and the reference-video mechanism, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers what the skill does, but the 'when to use it' trigger is missing from the description (it lives only in the body's Trigger Keywords section); per the judging guideline a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('Pixar-style', 'cartoon character', 'animate', 'dance', 'motion video') but lacks an explicit 'Use when...' clause and misses common user variations, fitting the 'some relevant keywords but missing common variations' anchor rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The two-phase photo-to-cartoon-to-dance-video pipeline is a distinct niche unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/cartoon-dance-animation/SKILL.md
Commit: 71242e2

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.