Conciseness

The ~107-line body is lean throughout: every section (Mental model, Golden rules, Order semantics, Troubleshooting) carries operational facts Claude would not know, with zero padding or explanation of known concepts. Not 4 because there are no passages that could be trimmed without losing information.

Actionability

The end-to-end flow block gives copy-paste-ready commands ('blockrun_polymarket action:"buy" token_id:"..." amount_usd:2 confirm:true') covering the common cases — fund, buy, limit orders, cancel, positions, redeem, withdraw — with only dynamic ids as placeholders, which is unavoidable. Not 4 because the commands are directly executable and cover the common cases, not merely 'mostly' executable.

Workflow Clarity

A clearly numbered 0–8 sequence with explicit validation gating: 'Call once WITHOUT confirm → show the dry-run preview → ask → re-call with confirm:true', satisfying the destructive-operation validation requirement for real-money trades. The Troubleshooting section maps concrete error strings to corrective actions ('No deposit wallet configured' → run action:"setup"), providing feedback loops for error recovery. Not 4 because checkpoints and recovery paths are explicit and complete.

Progressive Disclosure

No bundle files exist, and the single-file body is well-sectioned with clear headers and appropriate content placement; nothing that clearly belongs in a separate file is inlined. Not 5 because the ~100-line single-file skill exceeds the 'under 50 lines' case where organized sections alone earn a 5 — order-semantics or troubleshooting detail could plausibly live in reference files, so the structure is good but not the ideal reference-split example.

Specificity

The description lists multiple concrete actions — 'setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling' — with comprehensive coverage of the trading lifecycle. Not 4 because coverage of actions within its niche is complete, not just 'several with minor gaps'.

Completeness

It explicitly answers both: 'Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket' (when) and 'Covers setup..., buy/sell..., positions, redeeming winnings, geoblock handling, and the end-to-end flow' (what), with concrete trigger phrasing. Not 4 because the 'when' clause is explicit and specific, not merely present.

Trigger Term Quality

'PLACE, manage, or redeem bets on Polymarket' contains the natural phrases a user would say, giving good keyword coverage. Not 5 because synonyms and variations (e.g., 'trade', 'wager', 'cash out', 'positions') are only partially covered by 'buy/sell' and 'manage'.

Distinctiveness Conflict Risk

The parenthetical '(not just read odds — that's the blockrun_predexon_* data tools)' explicitly disambiguates this skill from the sibling data-lookup skill, establishing a clear niche with minimal conflict risk. Not 4 because the boundary is stated explicitly rather than merely implied by specificity.