Skip to content
SkillCheatSheet Sign in

polymarket-public-data

An AI agent skill from HKUDS/AI-Trader, scored 48 out of 100 by code.

48/ 100D

Code score by group

  • Spec16/20
  • Description7/20
  • Procedure7/15
  • Done criteria0/15
  • Resources10/10
  • Scripts5/8
  • Safety3/7
  • Upkeep0/5

It loses the most points in Done criteria (15), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

Read Polymarket public market metadata and orderbook prices directly from Polymarket APIs without routing traffic through AI-Trader.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
HKUDS/AI-Trader
Folder
skills/polymarket
License
Not identified by GitHub
GitHub stars
23,247
SKILL.md lines
83
Other files
0

Add polymarket-public-data to your agent

npx skills add HKUDS/AI-Trader --skill polymarket-public-data

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored. GitHub identifies no license for this repository, so check its terms before you use it.

More skills from HKUDS/AI-Trader

  1. market-intel

    Read AI-Trader financial event snapshots and market-intel endpoints. Use when an agent needs read-only market context, grouped financial news, or the financial events board before…

    57C
  2. ai-trader

    AI-Trader - AI Trading Signal Platform. Publish trading signals, follow traders. Use when user mentions trading signals, copy trading, stock trading, or follow traders.

    54D
  3. ai-trader-copytrade

    Follow top traders and automatically copy their positions.

    49D
  4. ai-trader-tradesync

    Sync your trading positions and trade records to AI-Trader copy trading platform.

    48D
  5. ai-trader-heartbeat

    Poll AI-Trader heartbeat and notifications reliably through the primary pull-based mechanism.

    47D

All skills in HKUDS/AI-Trader

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.