Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a well-structured, actionable two-phase recipe with concrete model IDs, complete prompts, and an explicit user-approval checkpoint. Its main gaps are the absence of error-recovery guidance for failed or off-target generations and slightly non-executable invocation forms (parameter lists and a templated curl body).
Suggestions
Show complete command-line examples (e.g. muapi image edit --model nano-banana-2-edit --reference-image <url> --prompt "..." ) so invocations are copy-paste ready instead of parameter bullet lists.
Add an error-recovery checkpoint: what to do if a generation request fails or the cartoon does not preserve identity (retry with adjusted prompt, or re-run with a stronger negative prompt).
Move the very long Phase A prompt (and its negative prompt) into a reference file (e.g. references/prompts.md) to reduce body length, and drop or fold the 'Trigger Keywords' section into the description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and assumes Claude's competence: no concept explanations, and the long prompt strings are executable payload rather than padding. Minor trimming is possible (the 'Trigger Keywords' section largely belongs in the description, and prompt boilerplate repeats identity-preservation instructions several times), placing it just below the lean 5 anchor. | 4 / 5 |
Actionability | Guidance is mostly executable: specific CLI commands with model IDs (muapi image edit model=nano-banana-2-edit, kling-v2.6-std-motion-control), full copy-paste prompts, negative prompts, and a curl fallback with polling. Not a 5 because invocations are given as parameter bullet lists rather than complete command lines, and the curl fallback contains a literal '{...}' JSON placeholder that is not copy-paste ready. | 4 / 5 |
Workflow Clarity | A clear two-phase sequence (cartoonify, present for user approval, gather reference video, animate, present final video) with an explicit approval checkpoint between phases. It misses the 5 anchor because there are no error-recovery steps if generation fails or the output does not match the reference motion. | 4 / 5 |
Progressive Disclosure | The body is well-organized into Inputs, Steps, Trigger Keywords, and Notes with no bundle files to reference (references/, scripts/, assets/ do not exist), so no navigation debt exists. It is not a 5 because the body slightly exceeds the under-50-line simple-skill threshold and the very long phase prompts would be cleaner in a separate reference file, a minor organization gap. | 4 / 5 |
Total | 16 / 20 Passed |