Content
68%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 body is efficient and highly actionable, with concrete commands, models, exact ad dimensions, and a clear two-phase workflow gated by user confirmation. Its main gap is the absence of any output verification or failure handling after the batch Phase B crops, plus some organizational sloppiness (stray divider, split Notes sections, undefined 'plan' submission mechanic).
Suggestions
Add a verification step after the Phase B batch crops — e.g. check each crop kept the product centered and uncropped, and re-run any failed format — to lift workflow clarity past the batch-operation cap.
Define the 'submit a plan' mechanism once (what tool/format the plan goes to) or replace it with direct executable muapi command lines for both phases, matching the curl fallback's concreteness.
Merge the two Notes sections and remove the stray '---' divider mid-file so the executing-agent guidance lives in one clearly labeled section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and table/step-driven with no explanations of concepts Claude already knows. Minor waste keeps it below 5: the line under the heading restates the description verbatim, 'Submit ONE the plan' is garbled phrasing, and two Notes sections are split by a stray '---' divider. | 4 / 5 |
Actionability | Concrete throughout: 'muapi image generate (model=nano-banana-pro)', exact aspect ratios with pixel dimensions, a copy-paste curl fallback, and a fully quoted crop prompt template. Below anchor 5 because the 'submit a/the plan' mechanism is never defined and no complete primary-path command line is shown, only fragments. | 4 / 5 |
Workflow Clarity | The two phases are clearly sequenced with an explicit human checkpoint ('Ask which copy variation to use for Phase B. Wait for user confirmation.' and 'Do NOT auto-confirm Phase B'). However, Phase B is a batch operation — 'All crops run in parallel' across four formats — with no output verification or error-recovery step, which caps workflow clarity at 3 per the rubric's batch-operations rule. | 3 / 5 |
Progressive Disclosure | The skill is self-contained and well-sectioned (Inputs, Steps, Notes, Trigger Keywords) with no external references, and none are needed — verified no bundle files exist so no referenced paths are broken. The awkward mid-file '---' divider and duplicated Notes sections, plus being slightly over the ~50-line simple-skill bar, keep it at 4 rather than 5. | 4 / 5 |
Total | 15 / 20 Passed |