Install
$ agentstack add skill-superior-trade-superior-skills-probability-mean-reversion ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Strategy: Polymarket · Probability Mean Reversion
When to use
Use this when someone asks for fade, overreaction, mean reversion, range trading, panic buy, euphoria selloff, or probability jumps with weak follow-through.
What the agent should look for
- Exact market slug from
POST /v3/markets/search. - A stable market with enough historical fills.
- Probability significantly far from a rolling median.
- Weak follow-through after the jump.
- No fresh catalyst changing the thesis.
- Enough time before resolution to allow drift back.
Backtest fit with filled data
Moderate fit. Filled TradeTick history can test whether probability moves have a measurable reversion pattern, while using actual fills as the execution proxy.
Limit: backtests cannot validate resting liquidity, spread paid, or what is missed in the maker queue.
Strategy logic
Enter when the outcome trades below a lower band and exit near the rolling median. If your implementation permits, do the inverse for above-band conditions when downside overextension appears.
Nautilus strategy shape
- Keep a rolling window of trade prices.
- Compute median and deviation thresholds.
- Enter only after sufficient tick history is collected.
- Exit on median reversion or max holding ticks.
Example strategyConfig
{
"window_ticks": 40,
"entry_deviation": 0.08,
"exit_deviation": 0.02,
"order_size": 10,
"max_holding_ticks": 80
}
Iteration knobs
| Knob | Effect | |---|---| | window_ticks | Larger windows produce a smoother baseline. | | entry_deviation | Higher values wait for stronger overreactions. | | exit_deviation | Lower values demand tighter reversion before exit. | | max_holding_ticks | Prevents stale positions through stale conditions. |
Failure modes
- Real information shocks rarely mean-revert.
- Markets near resolution can trend cleanly to 0 or 1.
- Low liquidity can create fake extremes.
- Backtests may look strong when spread and order-book pressure are ignored.
User-facing framing
"This is an overreaction fade. It works best in noisy markets without new decisive information. I’ll backtest it on filled prices first, then verify trade frequency and liquidity before suggesting live use."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Superior-Trade
- Source: Superior-Trade/superior-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.