jeremylongshore/tons-of-skills-marketplace / plugins/crypto/arbitrage-opportunity-finder/skills/finding-arbitrage-opportunities
finding-arbitrage-opportunities
VerifiedCompare live best bid and ask for one crypto pair across exchanges and report every cross-venue spread, gross and net of stated taker fees; search three-trade cycles within one exchange. Read-only, no API keys. Use when checking whether a coin trades at different prices on different exchanges, sizing a spread against fees, or looking for triangular price gaps on OKX, KuCoin or Gate. Trigger with phrases like "find arbitrage", "scan for arb", "price spread", "exchange price difference", "triangular arb", or "cross-exchange spread".
| File | Kind | Size |
|---|---|---|
| ARD.md | markdown | 2.2 KB |
| PRD.md | markdown | 2.4 KB |
| SKILL.md | skill md | 6.0 KB |
| assets/demo-recording.json | config | 42.6 KB |
| references/errors.md | markdown | 2.3 KB |
| references/examples.md | markdown | 12.8 KB |
| references/implementation.md | markdown | 4.4 KB |
| scripts/arb_finder.py | script | 17.7 KB |
| scripts/http_client.py | script | 6.4 KB |
| scripts/record_demo.py | script | 2.1 KB |
| scripts/spot_venues.py | script | 9.9 KB |
| scripts/spreads.py | script | 7.0 KB |
| tests/fixtures/binance-bybit-recording.json | config | 1.4 KB |
| tests/test_arb_finder.py | script | 9.9 KB |
PRD.md
View on GitHub# PRD: Arbitrage Opportunity Finder
> Part of [Tons of Skills](https://tonsofskills.com) by [Intent Solutions](https://intentsolutions.io) | [jeremylongshore.com](https://jeremylongshore.com)
## Summary
**One-liner**: Compare live best bid and ask for one crypto pair across exchanges and show every spread, gross and net of stated fees.
**Domain**: Cryptocurrency market research
**Users**: Traders and analysts checking whether price gaps between venues survive fees
## Problem Statement
Price gaps between exchanges are small and short-lived, and most of them disappear once fees are counted. Checking means opening several exchange pages, matching the exact pair (USD, USDT and USDC markets differ), and knowing each venue's fee. Version 1.x of this skill did not help: it read every price from a hard-coded table, even in "live" mode.
## Users
- **Trader**: wants to see quickly whether any venue pair stays positive after fees, before doing their own checks.
- **Researcher**: wants sourced, reproducible spread measurements.
- **Developer**: wants JSON to feed their own analysis.
## Requirements
### Must
1. Prices come from public, keyless order-book endpoints, with source URLs and fetch time.
2. Only identical pairs are compared.
3. Every spread is shown gross and net; each fee assumption names its source. A venue whose fee cannot be confirmed shows `n/a` net until the user sets it.
4. A failing venue is named with a plain reason; no price is substituted.
5. No mock prices by default; recorded data only behind `--demo`, marked on every line.
6. No order, account, withdrawal or signing code; a test enforces it.
7. Every report lists what is not included (withdrawal fees, transfer time, price moves, depth) and ends with "Research output only. Not financial advice. This tool places no trades."
8. Standard library only; Python 3.9+.
### Should
1. Size available at the best prices for each spread.
2. Triangular search on venues that publish full ticker lists, with a volume floor.
3. Offline tests replaying recorded real responses.
### Will not
- Execute trades, simulate executions, or use flash loans.
- DEX or cross-chain prices (no reliable keyless source).
## Success criteria
- From a US network, at least five venues quote BTC/USDT (seven did on 2026-10-25); from a network Binance and Bybit serve, all nine (verified from France).
- `python3 -m unittest discover -s tests` passes offline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |