poly-market-data

Validate Polymarket trades and CLOB state against on-chain events.

4|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill poly-market-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: poly-market-data
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/poly-market-data
Command: npx skills add https://github.com/cogni-dao/cogni --skill poly-market-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Polymarket data-ground truth extraction and CLOB semantics verification to reliably align on-chain events with the Polymarket Data-API, enabling accurate debugging, wallet screening, and cross-system auditing.

Core Features & Use Cases

  • Ground-truth validation across trades, positions, and on-chain state using Polymarket Data-API and CLOB data.
  • Wire-level order semantics and per-tenant wallet workflows, including EOAs vs Safe proxies, for testing and debugging trading interfaces.
  • Supports integration points with mirror and wallet provisioning components (poly-copy-trading, poly-auth-wallets) for end-to-end validation.

Quick Start

Query the latest Polymarket trades and positions, and correlate them with on-chain events to verify market state.

Frequently Asked Questions about poly-market-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Polymarket ground-truth data between the Data-API and on-chain events?

To extract authoritative Polymarket market data, you query the Data-API and CLOB state, correlating fields like tokenId, side, price, and size with on-chain events to verify ground-truth across trades and positions.

What is the best way to debug Polymarket wallet activity distinguishing between EOAs and Safe proxies?

Debugging Polymarket wallet activity requires cross-dataset correlation to differentiate externally owned accounts (EOAs) from Safe proxies. This per-tenant workflow validates wire-level order semantics and screens wallet activity accurately.

How do I use Polymarket CLOB fields like client_order_id and time_in_force for testing workflows?

Polymarket CLOB fields including client_order_id and time_in_force are mapped to drive testing workflows. These wire-level order semantics validate trading interfaces and feed downstream components like poly-copy-trading and poly-auth-wallets.

Why does my Polymarket on-chain state show inconsistencies with Data-API trade records?

Polymarket on-chain state and Data-API inconsistencies arise from misaligned cross-dataset correlation. Applying ground-truth validation across trades, positions, and wallets using CLOB data resolves these ordering and activity discrepancies.

Can I use Polymarket Data-API to screen wallets and audit cross-system trading interfaces?

Yes, the Polymarket Data-API enables wallet screening and cross-system auditing by extracting ground-truth data. It validates on-chain events against CLOB semantics to reliably debug and audit per-tenant wallet workflows.