# Polymarket Clob Order Routing

> Automated Polymarket CLOB v2 order creation, signature signing, and REST API routing

- Skill: `knuckles-team/polymarket-clob-order-routing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add knuckles-team/polymarket-clob-order-routing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/knuckles-team/polymarket-clob-order-routing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: Knuckles-Team (https://skillmd.com/u/knuckles-team)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/knuckles-team/polymarket-clob-order-routing

---


# polymarket-clob-order-routing Workflow

Automated Polymarket CLOB v2 order creation, signature signing, and REST API routing

### Step 0: initialize-clob-client [skill: emerald-exchange]
Initialize CLOB Client & API credentials using EIP-712 wallet signatures
Expected: clob_client_creds

### Step 1: mcp_market_data [depends_on: Step 0]
Fetch current Polymarket order book depth and spreads
Expected: market_quote

### Step 2: mcp_orders [depends_on: Step 1]
Construct and cryptographically sign limit or market order parameters
Expected: signed_order_payload

### Step 3: submit-clob-order [skill: emerald-exchange] [depends_on: Step 2]
Submit signed order payload to the Polymarket CLOB REST endpoint
Expected: execution_result

### Step 4: mcp_portfolio [depends_on: Step 3]
Query active position ledger to verify fill status and update balances
Expected: filled_position_data

## Execution

Run this workflow as a dependency-ordered DAG. Steps with no unmet `depends_on` run in parallel; dependents run after their prerequisites complete.

- **Run first (in parallel):** Step 0 — initialize-clob-client
- **After level 0:** Step 1 — mcp_market_data
- **After level 1:** Step 2 — mcp_orders
- **After level 2:** Step 3 — submit-clob-order
- **After level 3:** Step 4 — mcp_portfolio

**Execution:** If graph-os is reachable, offload the whole DAG via `graph_orchestrate action=execute_workflow` (or the `kg-delegate` skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet `depends_on` in parallel, then their dependents.