菜单
evaluate whether passive polymarket quoting looks reward-eligible or operationally sensible. use when the user wants market-making guidance, passive quote placement, spread analysis, rewards checks, or two-sided quoting ideas.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | maker-rewards-check |
| description | evaluate whether passive polymarket quoting looks reward-eligible or operationally sensible. use when the user wants market-making guidance, passive quote placement, spread analysis, rewards checks, or two-sided quoting ideas. |
Use this skill to answer one question:
is passive quoting in this market actually attractive, reward-eligible, and operationally survivable?
This skill is the passive-liquidity layer:
strategy-draftorder-ticket when the user wants a concrete quote planIt should evaluate maker quality, not drift into generic taker trading.
Use this skill when the user is effectively asking:
Use this skill for:
Do not use this skill to:
Do not finalize the check until you have, or explicitly mark as missing:
Before evaluating, inspect the market from these lenses:
Use the minimum live set needed:
get_market_snapshotget_orderbookget_recent_tradesget_rewards_status when availableIf the main missing piece is:
strategy-draftorder-ticketmarket-memoWrite a 1-2 line intent statement for yourself covering:
Confirm:
When available, use get_rewards_status to determine:
If rewards data is unavailable, say so clearly and continue with operational analysis only.
At minimum, assess:
Summarize:
order-ticketReturn exactly these sections in this order.
State in 1-2 sentences:
List:
List:
Keep this high-level:
List:
Choose one:
maker-rewards-checkmarket-memostrategy-draftorder-ticketExplain why that is the cheapest useful next step.
The maker check is complete only when:
market-memo — use when the user first needs a broader live-state read on the marketstrategy-draft — use when the real question is directional strategy, not maker quotingorder-ticket — use when quote logic is ready to become a guarded preview plandiscover, filter, sort, and shortlist polymarket markets from the full active market universe. use when the user wants to browse all available bets, find candidates by category, horizon, liquidity, structure, catalyst profile, resolution risk, opportunity type, create discovery-driven watchlists, or run scheduled universe triage before deeper research. do not use for placing, previewing, or submitting trades.
perform deep research for a polymarket market, event, or thesis. use when the user wants fair-value work, evidence gathering, catalyst mapping, linked-market comparisons, or a detailed explanation of whether the market looks mispriced. for wide candidate sets or triage questions, use opportunity-classifier first.
write a structured memo for a polymarket market or event. use when the user asks to analyze a single market, summarize current odds, liquidity, spread, recent flow, resolution mechanics, or prepare a trade brief before acting. for broad candidate sets or ranking questions, use opportunity-classifier first.
turn a polymarket strategy into a guarded order plan. use when the user wants a limit order, marketable order, preview, cancel plan, or explicit trade parameters. use this skill before any live execution.
review polymarket positions, open orders, and concentration risk. use when the user asks what they own, where they are overexposed, which orders are stale, how correlated their book is, or what should be reduced or canceled. when helpful, reuse the opportunity-classifier taxonomy to bucket exposure by structural type, horizon, and resolution risk.
monitor polymarket markets that are close to resolution or likely to be resolved soon. use when the user wants official-source checking, resolution readiness, ambiguity flags, or a scheduled workflow for near-resolution markets.