Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, actionable, well-organized skill body; the main gap is that the async generation workflow is flagged but never explained or sequenced.
Suggestions
Add a brief async workflow example showing how to submit a job, retrieve the job ID, and poll for the result when using `--async`.
Document what the common flags (`--async`, `--view`, `--json`, `--timeout`) actually do, or point to `--help` for the detail.
Clarify error handling when `MUAPI_KEY` is unset or an API call fails, so Claude can recover rather than abort.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — a script table, quick-start commands, flags, and requirements — with no explanation of concepts Claude already knows; every section earns its place. | 3 / 3 |
Actionability | Quick-start gives concrete, copy-paste-ready commands (e.g. `bash generate-image.sh --prompt "..." --model flux-dev --view`) with real flags, matching the fully-executable anchor. | 3 / 3 |
Workflow Clarity | Each script is a single action, but the listed `--async` flag implies a submit/poll/retrieve multi-step workflow that is never sequenced, leaving a checkpoint gap for async generation. | 2 / 3 |
Progressive Disclosure | A short (<50 line), well-sectioned single overview file with no need for external reference files, satisfying the simple-skill exception for progressive disclosure. | 3 / 3 |
Total | 11 / 12 Passed |