Content
77%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.
Highly actionable content with an explicit, well-validated async workflow and excellent error-recovery guidance. It is dragged down by verbosity (repetitive example blocks and a generic prompt-writing tutorial) and a monolithic structure that inlines material better kept in separate reference files.
Suggestions
Move the model catalog, prompt best practices, and common-scenario examples into references/ files (e.g. MODELS.md, PROMPTS.md) and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.
Cut the nine near-duplicate bash invocations down to one or two canonical examples plus the parameter table, and drop the prompt-writing tutorial that restates what Claude already knows.
Trim marketing-style padding such as '无需安装任何依赖!' and duplicated setup notes to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient (limit tables, error/fix pairs, and parameter tables earn their tokens), but includes nine near-identical bash invocations across the examples and 'common scenarios' sections, a prompt-writing tutorial that mostly teaches what Claude already knows, and marketing padding ('无需安装任何依赖!'). This fits the 'mostly efficient but some unnecessary explanation or could be tightened' anchor rather than anchor 4's 'minor instances'. | 3 / 5 |
Actionability | Every workflow is a fully executable, copy-paste-ready bash command against the real bundled script (scripts/generate-video.sh exists and delegates to generate_video.js), with real model IDs, complete flag tables, status tables, and cause-to-solution error pairs covering the common cases. Matches anchor 5. | 5 / 5 |
Workflow Clarity | The async workflow is explicitly sequenced (submit task → poll status → download video), with a status table mapping each state (queued/running/succeeded/failed) to the action to take and an error-handling section giving recovery guidance per failure mode. These feedback loops for error recovery match anchor 5 rather than anchor 4's 'minor validation gaps'. | 5 / 5 |
Progressive Disclosure | The file is well-sectioned with headers and correctly references the bundled scripts, but it is a ~450-line monolith: the model catalog, prompt best-practices tutorial, and common-scenario examples are all inlined when they belong in separate reference files, and no references/ files exist in the bundle. This matches anchor 3 ('content that should be separate is inline') better than anchor 4. | 3 / 5 |
Total | 16 / 20 Passed |