/polymarket
Query Polymarket prediction markets — search events, check odds and prices, view trending markets, track price momentum, get orderbook depth, analyze volume, and monitor market resolution timelines. Use when the user asks about prediction markets, betting odds, event
$ npx -y skills add CoWork-OS/CoWork-OS --skill polymarket --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/polymarket
Context preview
The summary Claude sees to decide when to auto-load this skill.
Query Polymarket prediction markets — search events, check odds and prices, view trending markets, track price momentum, get orderbook depth, analyze volume, and monitor market resolution timelines. Use when the user asks about prediction markets, betting odds, event
SKILL.md
polymarket.SKILL.mdname: polymarket
description: "Query Polymarket prediction markets — search events, check odds and prices, view trending markets, track price momentum, get orderbook depth, analyze volume, and monitor market resolution timelines. Use when the user asks about prediction markets, betting odds, event probabilities, or Polymarket data."
Polymarket
Purpose
Query Polymarket prediction markets — search events, check odds and prices, view trending markets, track price momentum, get orderbook depth, analyze volume, and monitor market resolution timelines. Use when the user asks about prediction markets, betting odds, event probabilities, or Polymarket data.
Routing
- Use when: User asks about prediction markets, betting odds, event probabilities, Polymarket data, what markets think about something, or wants to check odds on any topic
- Do not use when: User is asking about stock market prices, crypto token prices (not prediction markets), or wants to place actual trades
- Outputs: Market odds, trending events, price movements, orderbook data, resolution timelines
- Success criteria: User receives clear, formatted prediction market data with probabilities shown as percentages
Trigger Examples
Positive
- Use the polymarket skill for this request.
- Help me with polymarket.
- User asks about prediction markets, betting odds, event probabilities, Polymarket data, what markets think about something, or wants to check odds on any topic
- Polymarket: provide an actionable result.
Negative
- User is asking about stock market prices, crypto token prices (not prediction markets), or wants to place actual trades
- Do not use polymarket for unrelated requests.
- This request is outside polymarket scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | No | What to search for or ask about (e.g., 'Trump election odds', 'trending crypto markets', 'AI predictions') |
Runtime Prompt
- Current runtime prompt length: 867 characters.
- Runtime prompt is defined directly in `../polymarket.json`.
Read more
name: polymarket description: "Query Polymarket prediction markets — search events, check odds and prices, view trending markets, track price momentum, get orderbook depth, analyze volume, and monitor market resolution timelines. Use when the user asks about prediction markets, betting odds, event probabilities, or Polymarket data."
Polymarket
Purpose
Query Polymarket prediction markets — search events, check odds and prices, view trending markets, track price momentum, get orderbook depth, analyze volume, and monitor market resolution timelines. Use when the user asks about prediction markets, betting odds, event probabilities, or Polymarket data.
Routing
- Use when: User asks about prediction markets, betting odds, event probabilities, Polymarket data, what markets think about something, or wants to check odds on any topic
- Do not use when: User is asking about stock market prices, crypto token prices (not prediction markets), or wants to place actual trades
- Outputs: Market odds, trending events, price movements, orderbook data, resolution timelines
- Success criteria: User receives clear, formatted prediction market data with probabilities shown as percentages
Trigger Examples
Positive
- Use the polymarket skill for this request.
- Help me with polymarket.
- User asks about prediction markets, betting odds, event probabilities, Polymarket data, what markets think about something, or wants to check odds on any topic
- Polymarket: provide an actionable result.
Negative
- User is asking about stock market prices, crypto token prices (not prediction markets), or wants to place actual trades
- Do not use polymarket for unrelated requests.
- This request is outside polymarket scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | query | string | No | What to search for or ask about (e.g., 'Trump election odds', 'trending crypto markets', 'AI predictions') |
Runtime Prompt
- Current runtime prompt length: 867 characters.
- Runtime prompt is defined directly in `../polymarket.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill