luckylobster-skill_skill

This skill helps you trade Polymarket markets by searching, placing orders, and managing positions securely through LuckyLobster.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill luckylobster-skill

  • _meta.json820 B
  • skill.md38.0 KB

Overview

This skill lets an agent search Polymarket prediction markets, place orders, and manage positions via a secure API. It supports device-based authentication, real-time market data, and CLOB trading primitives so agents can trade outcome tokens programmatically. It is designed for automated traders that need fast market discovery and order execution on Polymarket.

How this skill works

The skill uses a REST API with an API key obtained through a device authorization flow; agents request a device code, direct the user to the verification URL, then poll for the returned API key. Once authorized, the skill calls endpoints to search markets, fetch market details and token IDs, retrieve order books/prices/spreads, and submit orders (LIMIT, MARKET, FOK, FAK). WebSocket-backed real-time data is used when available to reduce latency for open positions.

When to use it

  • Automatically discover and trade Polymarket markets from natural-language queries.
  • Execute programmatic trading strategies using CLOB token IDs and live order books.
  • Monitor open positions and use cached websocket prices for low-latency decisions.
  • Quickly find deterministic crypto up/down markets (15m/hourly/daily) via the crypto endpoint.
  • Integrate prediction-market trades into portfolio or decision-making workflows.

Best practices

  • Use /markets/crypto for deterministic crypto markets instead of text search when available.
  • Always retrieve tokens[].tokenId or clobTokenIds from /markets/{id} before trading.
  • Save the API key persistently after device auth; it is returned only once.
  • Respect rate limits (default 100 requests/min) and inspect X-RateLimit headers to avoid throttling.
  • Prefer MARKET or FOK for quick fills and LIMIT for passive placement; check order status in the response.

Example use cases

  • Search for a high-liquidity election market, fetch token IDs, and place a limit buy on the favored outcome.
  • Monitor Bitcoin 15-minute up/down markets and place automated scalps using /markets/crypto and /prices.
  • Aggregate spreads and orderbook summaries across multiple tokens to detect arbitrage or liquidity imbalances.
  • Cancel or modify stale LIMIT orders programmatically and redeem settled winning positions.

FAQ

Use the device authorization flow: request a device code, give the user the verification_uri_complete link, then poll for an API key and store it persistently.

Which token ID should I use for trading?

Use the tokenId values found in the market details (tokens array) or the clobTokenIds field; these are required for order and market-data endpoints.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational