Content
78%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 strong example of an executable skill: concrete commands for every capability, a sensible decision workflow, and accurate pre-flight failure documentation. The main flaw is redundancy — the operator-only routing warning is repeated four times and padded onto every purpose bullet, which wastes tokens without adding information.
Suggestions
State the operator-only/shopping-copilot routing rule once (in Hard rules) and delete the duplicate bold warning and second paragraph at the top.
Drop the "(operator use)" suffix from all six purpose bullets since the section title and skill title already establish operator-only scope.
Fold the credential pre-flight check into the Suggested workflow as step 0 so the validation checkpoint sits inside the sequence rather than only in Hard rules.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The operator-only routing rule is stated four separate times ("This skill requires local Coupang API credentials. It is not for end-user shopping requests.", "Use `shopping-copilot` for all user-facing shopping queries...", "NEVER invoke this skill for general user shopping requests", plus the frontmatter), and all six purpose bullets redundantly append "(operator use)" when the section heading and title already establish it. This is anchor 3 (mostly efficient but could be tightened) rather than 4, since the repetition is noticeable rather than minor. | 3 / 5 |
Actionability | Six fully executable, copy-paste-ready commands with realistic arguments cover the common cases: search "생수", rocket "에어팟", budget "키보드" --max-price 100000, compare "아이패드 vs 갤럭시탭", goldbox, and a tools contract check. This matches anchor 5 exactly — specific examples covering the common cases with no gaps. | 5 / 5 |
Workflow Clarity | The five-step suggested workflow maps query shapes to commands ("If the query is too broad, narrow by use case, budget, or rocket-delivery preference", "Use `budget` when the user gives a price ceiling"), and Hard rules document a pre-flight checkpoint ("will fail with `RuntimeError: Coupang credentials are required` ... check env before invoking"). Anchor 4 rather than 5 because the env validation and `tools` contract check live in Hard rules instead of being integrated as explicit checkpoints in the workflow sequence, and there is no error-recovery loop. | 4 / 5 |
Progressive Disclosure | The body is short and cleanly sectioned (purpose, hard rules, commands, workflow) with nothing that belongs in a separate file, and every command references the single real bundle script (scripts/openclaw-coupang-mcp.py, verified to exist). Per the simple-skill note, a short skill with no need for external references and well-organized sections scores 5. | 5 / 5 |
Total | 17 / 20 Passed |