mcpbeat

Probability Momentum

superior-trade/probability-momentum

Use when a Polymarket outcome price and filled volume are accelerating in the same direction.

677 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
225
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Superior-Trade/superior-skills --skill probability-momentum

The instruction itself

10 sections, as written by the author

Strategy: Polymarket · Probability Momentum

When to use

Use this when someone asks for momentum, trend following, breakout, follow-the-crowd behavior, fast-moving crypto milestones, or rapid probability acceleration.

What the agent should look for

  • Exact market slug from POST /v3/markets/search.
  • backtestSupported: true.
  • Sufficient filled-trade history for the requested lookback window.
  • Rising probability on last-trade filled ticks.
  • Elevated fill counts or larger notional during the move.
  • Market not too close to resolution unless user explicitly accepts expiry risk.

Backtest fit with filled data

Good fit for this archetype. Filled TradeTick history can validate whether momentum would have produced fill-driven entries, exits, and directional exposure.

Limit: filled-trade backtests do not prove maker queue position, maker rebates, or order-book depth. Treat this as taker-style behavior evidence, not certainty.

Strategy logic

Enter YES when recent probability rises more than a threshold over lookback_ticks. Exit when exit_after_ticks is reached, or when momentum stalls if an exit condition is included.

Nautilus strategy shape

  • subscribe_trade_ticks(instrument_id) to stream TradeTicks.
  • Use on_trade_tick as the main event handler.
  • Submit market or conservative IOC orders.
  • Track open position and fill state in on_order_filled.

Example strategyConfig

{
  "lookback_ticks": 5,
  "momentum_threshold": 0.02,
  "order_size": 10,
  "exit_after_ticks": 25,
  "max_entries": 3
}

Iteration knobs

| Knob | Effect |

|---|---|

| lookback_ticks | Larger values reduce noise; smaller values react faster. |

| momentum_threshold | Higher values reduce frequency and require stronger momentum. |

| order_size | Larger values increase PnL sensitivity and liquidity exposure. |

| exit_after_ticks | Shorter values trim quickly; longer values hold trend. |

| max_entries | Caps repeated entries in choppy markets. |

Failure modes

  • One large fill can produce a false momentum signal.
  • Thin trades can overstate available liquidity.
  • Late-resolution markets can reverse from mark-to-market gains to a 0/1 close.
  • Stale fills can make momentum look cleaner than it was live.

User-facing framing

"This is a probability momentum strategy: it buys when fills and last-trade probability move together in one direction. It is backtestable with filled TradeTicks, but it does not confirm maker queue priority or spread capture."

How to use it

Copy the folder

Take superior-trade/probability-momentum from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.