Content
46%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 delivers highly actionable, executable Polymarket trading code, but it is a monolithic ~1080-line reference that duplicates its own method catalog and inlines everything that should live in separate reference files. Workflow guidance lacks explicit validation checkpoints for real-money operations, and token efficiency suffers badly from the double documentation.
Suggestions
Split the method reference tables, WebSocket guide, and on-chain helpers into references/ files (e.g., references/methods.md, references/websockets.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.
Remove the duplication between the prose API sections and the "Complete ClobClient Method Reference" tables — keep one canonical form.
Add explicit pre-trade validation steps and fix-and-retry loops (e.g., check balance/allowance → calculate_market_price → post → verify fill status) to the trading workflow, since orders move real money.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~1080-line body documents the entire 60+-method API twice — once in prose/code sections and again in the "Complete ClobClient Method Reference" tables — plus exhaustive WebSocket and on-chain sections, which is noticeably verbose with substantial duplicated padding. It avoids anchor 1 only because it does not explain concepts Claude already knows; it stays at 2 rather than 3 because the duplication is a major, systematic token waste rather than minor tightening. | 2 / 5 |
Actionability | Nearly all code is concrete and copy-paste executable (client initialization, order placement, cancels, WebSocket auth, eth_call balance checks), matching anchor 4. It falls short of 5 due to minor gaps, e.g., in "Create and Post Orders" the block `result = client.create_market_order(...)` never posts the signed order, so copying it silently places nothing. | 4 / 5 |
Workflow Clarity | The "Complete Trading Example" provides a rough sequence (check position → fetch book → place order) and an error-handling section lists common errors, but there are no explicit pre-trade validation checkpoints or fix-and-retry feedback loops. Since this skill places real-money orders and includes destructive/batch operations (`cancel_all`, market orders), the missing-validation guideline caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), and the full method catalog, WebSocket guide, and contract tables are all inlined in SKILL.md — content that clearly belongs in separate files. Section headers exist (so not anchor 1), but with no references at all and hundreds of lines of inline API reference, this matches anchor 2 rather than 3. | 2 / 5 |
Total | 11 / 20 Passed |