Content
53%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 a lean, well-organized catalogue advertisement, but it defers everything substantive to the upstream repository and its single "command" (`open <url>`) is neither executable nor an installation step. The result is a skill whose content tells the agent what it advertises but not how to do anything.
Suggestions
Replace the `open https://github.com/MiniMax-AI/skills` snippet with a concrete, executable install step (e.g. `git clone` into a specific skills-directory path, or the exact subpath of the upstream bundle to copy).
Inline a minimal quick-start (the MiniMax API call or a single example command for converting one photo) so the skill is actionable even before the upstream bundle is installed.
Drop the verbatim duplicate of the frontmatter description in "What it does" and merge the "Source" section into it, since the upstream URL and category are already in the frontmatter.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short (~25 lines) with clean sections and no tutorials on concepts Claude already knows. Not 5 because it duplicates the frontmatter description verbatim in "What it does" and repeats the upstream URL and category in "Source", padding that could be trimmed. | 4 / 5 |
Actionability | The only command is "open https://github.com/MiniMax-AI/skills" — a browser-open that is not executable on most agent hosts and installs nothing; the body says to "install the upstream bundle into your active agent's skills directory" but gives no install command, path, or any concrete step of the actual sticker-making workflow. This is high-level direction missing the specific steps to execute (score-2 anchor), not 3 because there is no partially-executable guidance at all. | 2 / 5 |
Workflow Clarity | A rough sequence exists (inspect upstream README → install the bundle → invoke by name or trigger phrase), but each step is under-specified: no install command, no destination path, no verification that the bundle landed. The single-action simplicity exception does not lift it to 5 because the one action (installing the upstream bundle) is itself ambiguous and punts to an external repo. | 3 / 5 |
Progressive Disclosure | No local bundle files exist (no references/, scripts/, or assets/), and the short body is organized into clearly headed sections (What it does / Source / How to use) with the upstream reference clearly signaled one level deep. Not 5 because the entire substantive payload is deferred to an external URL with no local content or navigable structure to split — the "How to use" section is a pointer, not an overview plus content. | 4 / 5 |
Total | 13 / 20 Passed |