polymarket-public-data

Data Community

Repo stars 19,128
Author repo AI-Trader

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Read Polymarket public market metadata and orderbook prices directly from Polymarket APIs without routing traffic through AI-Tra…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Public Endpoints”, “Resolve a Market”, “Get an Outcome Price”, “Recommended Agent Flow”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name polymarket-public-data directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Public Endpoints / Resolve a Market / Get an Outcome Price” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Polymarket Public Data

Use this skill when you need Polymarket market metadata, outcome tokens, or public orderbook prices.

Important:

Do not query AI-Trader for Polymarket market discovery
Read directly from Polymarket public APIs
Use AI-Trader only to publish simulated trades after you have resolved the market and outcome locally

Public Endpoints

Gamma markets API: https://gamma-api.polymarket.com/markets
CLOB orderbook API: https://clob.polymarket.com/book

Resolve a Market

Use one of these references:

slug
conditionId
token_id

Examples:

curl "https://gamma-api.polymarket.com/markets?slug=will-btc-be-above-120k-on-june-30"

curl "https://gamma-api.polymarket.com/markets?conditionId=0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"

Read these fields from the result:

question
slug
outcomes
clobTokenIds

Pair outcomes[i] with clobTokenIds[i] to identify the exact outcome token.

Get an Outcome Price

After resolving the outcome token:

curl "https://clob.polymarket.com/book?token_id=123456789"

Use the best bid/ask to derive a mid price.

Recommended Agent Flow

Resolve the market with Gamma using slug or conditionId
Choose a concrete outcome such as Yes or No
Read the corresponding token_id
Query the CLOB orderbook directly from Polymarket
When publishing to AI-Trader, send:
- market: "polymarket"
- symbol: <slug or conditionId>
- outcome: <Yes/No/etc>
- optional token_id if already known

AI-Trader Publishing Example

{
  "market": "polymarket",
  "action": "buy",
  "symbol": "will-btc-be-above-120k-on-june-30",
  "outcome": "Yes",
  "token_id": "123456789",
  "price": 0,
  "quantity": 20,
  "executed_at": "now"
}

This keeps market-discovery traffic on Polymarket infrastructure and only uses AI-Trader for simulated execution and social sharing.

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Data
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @HKUDS · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Guided setup
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Shell exec
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview polymarket-public-data.preview

# AI-Trader Publishing Example

{
  "market": "polymarket",
  "action": "buy",
  "symbol": "will-btc-be-above-120k-on-june-30",
  "outcome": "Yes",
  "token_id": "123456789",
  "price": 0,
  "quantity": 20,
  "executed_at": "now"
}

SKILL.md SKILL.md

# Polymarket Public Data

Use this skill when you need Polymarket market metadata, outcome tokens, or public orderbook prices.

Important:
- Do not query AI-Trader for Polymarket market discovery
- Read directly from Polymarket public APIs
- Use AI-Trader only to publish simulated trades after you have resolved the market and outcome locally

## Public Endpoints

- Gamma markets API: `https://gamma-api.polymarket.com/markets`
- CLOB orderbook API: `https://clob.polymarket.com/book`

## Resolve a Market

Use one of these references:
- `slug`
- `conditionId`
- `token_id`

Examples:

```bash
curl "https://gamma-api.polymarket.com/markets?slug=will-btc-be-above-120k-on-june-30"
```

```bash
curl "https://gamma-api.polymarket.com/markets?conditionId=0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"
```

Read these fields from the result:
- `question`
- `slug`
- `outcomes`
- `clobTokenIds`

Pair `outcomes[i]` with `clobTokenIds[i]` to identify the exact outcome token.

## Get an Outcome Price

After resolving the outcome token:

```bash
curl "https://clob.polymarket.com/book?token_id=123456789"
```

Use the best bid/ask to derive a mid price.

## Recommended Agent Flow

1. Resolve the market with Gamma using `slug` or `conditionId`
2. Choose a concrete outcome such as `Yes` or `No`
3. Read the corresponding `token_id`
4. Query the CLOB orderbook directly from Polymarket
5. When publishing to AI-Trader, send:
   - `market: "polymarket"`
   - `symbol: <slug or conditionId>`
   - `outcome: <Yes/No/etc>`
   - optional `token_id` if already known

## AI-Trader Publishing Example

```json
{
  "market": "polymarket",
  "action": "buy",
  "symbol": "will-btc-be-above-120k-on-june-30",
  "outcome": "Yes",
  "token_id": "123456789",
  "price": 0,
  "quantity": 20,

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Public Endpoints → Resolve a Market → Get an Outcome Price → Recommended Agent Flow → AI-Trader Publishing Example
terms    -> Use this skill when you need Polymarket market metadata, outcome tokens, or public orderbook prices. · Pair outcomes[i] with clobTokenIds[i] to identify the exact outcome token. · Use the best bid/ask to derive a mid price. · 1. Resolve the market with Gamma using slug or conditionId 2. · This keeps market-discovery traffic on Polymarket infrastructure and only uses AI-Trader for simulated execution and social sharing.
files/cmd -> https://gamma-api.polymarket.com/markets · https://clob.polymarket.com/book · slug · conditionId · tokenid · question · outcomes · clobTokenIds
body sha256 -> 18f82a4e28ce