Skip to content
Back to search

bytx-skills

MarketplaceWorks with Claude CodeGitHub

Crypto trading skills for AI assistants on bytx

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/byttrade--bytx-skills/badge.svg)](/listings/byttrade--bytx-skills)

HTML

<a href="/listings/byttrade--bytx-skills"><img src="/api/listings/byttrade--bytx-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

You need [uv](https://docs.astral.sh/uv/) (`brew install uv` or `curl -LsSf https://astral.sh/uv/install.sh | sh`).

**Any MCP client** (Claude Desktop, Claude Code, Cursor, …): add the server to the client's MCP config — templates in [`mcp-configs/`](mcp-configs/):

{ "mcpServers": { "bytx-trader": {
    "command": "uvx",
    "args": ["--refresh-package", "bytx", "--refresh-package", "bytx-trader",
             "--from", "bytx-trader@latest", "bytx-trader-mcp"] } } }

Restart the assistant and talk to it: "scan the crypto market", "switch to Bybit, 5 dollars risk per trade", "plan a long on ETH with a stop at 1.5 ATR", "what are my positions". Or start from the server's `trade_pipeline` prompt. Symbols can be written any way (`BTC`, `btcusdt`, `BTC/USDT`). Set the `confirm` tool to ask you every time. Without uv: `pip install bytx-trader` and `"command": "bytx-trader-mcp"`. Claude Desktop says the server failed to start? It may not see `uvx`: put the full path from `which uvx` in `"command"`.

**Claude only, on top of that:**

/plugin marketplace add byttrade/bytx-skills
/plugin install bytx-trader@bytx-skills

or copy the folders: `cp -r bytx-skills/crypto-* ~/.claude/skills/` (or your project's `.claude/skills/`).

| | any MCP client | Claude only | |---|---|---| | all eight steps, paper and demo | MCP tools | | | risk gate and one-time confirm token | in the server | | | the trade as a script | `trade_pipeline` prompt | skills | | `/crypto-*` commands, triggers by phrase, plugin install | | ✓ |

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "bytx-skills",
  4. "description": "Crypto trading skills for AI assistants on bytx",
  5. "owner": {"name": "BYTtrade", "url": "https://byttrade.com"},
  6. "plugins": [
  7. {
  8. "name": "bytx-trader",
  9. "description": "Crypto trading skills on bytx: scan, funding and open interest, entry, exit, time machine, size, risk, broker (paper by default, never without your yes).",
  10. "source": "./",
  11. "category": "productivity"
  12. }
  13. ]
  14. }
README.md · README · 138 lines · 1 finding marked
  1. # bytx-skills — crypto trading skills for AI assistants
  2. **English** | [Русский](docs/README.ru.md)
  3. Eight steps for one crypto trade, from "what's moving" to the order: scan the perps, read funding and open interest,
  4. time the entry, plan the exit, replay the rest of the session 10,000 times, size the position from the money you
  5. are ready to lose, check it against your limits, and send it — paper by default, never without your yes.
  6. Works with **any AI assistant that supports MCP — for example, Claude**. The logic is a Python package with an MCP
  7. server and a CLI on the [bytx](https://pypi.org/project/bytx/) exchange library; for Claude there are also skills
  8. (`/crypto-scanner` …) on top.
  9. Paper trading runs on the exchange's live order book with virtual money: no keys, no signup.
  10. ## Install
  11. You need [uv](https://docs.astral.sh/uv/) (`brew install uv` or `curl -LsSf https://astral.sh/uv/install.sh | sh`).
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 17 on GitHub
  12. **Any MCP client** (Claude Desktop, Claude Code, Cursor, …): add the server to the client's MCP config —
  13. templates in [`mcp-configs/`](mcp-configs/):
  14. ```json
  15. { "mcpServers": { "bytx-trader": {
  16. "command": "uvx",
  17. "args": ["--refresh-package", "bytx", "--refresh-package", "bytx-trader",
  18. "--from", "bytx-trader@latest", "bytx-trader-mcp"] } } }
  19. ```
  20. Restart the assistant and talk to it: "scan the crypto market", "switch to Bybit, 5 dollars risk per trade",
  21. "plan a long on ETH with a stop at 1.5 ATR", "what are my positions". Or start from the server's `trade_pipeline`
  22. prompt. Symbols can be written any way (`BTC`, `btcusdt`, `BTC/USDT`). Set the `confirm` tool to ask you every
  23. time. Without uv: `pip install bytx-trader` and `"command": "bytx-trader-mcp"`. Claude Desktop says the server
  24. failed to start? It may not see `uvx`: put the full path from `which uvx` in `"command"`.
  25. **Claude only, on top of that:**
  26. ```
  27. /plugin marketplace add byttrade/bytx-skills
  28. /plugin install bytx-trader@bytx-skills
  29. ```
  30. or copy the folders: `cp -r bytx-skills/crypto-* ~/.claude/skills/` (or your project's `.claude/skills/`).
  31. | | any MCP client | Claude only |
  32. |---|---|---|
  33. | all eight steps, paper and demo | MCP tools | |
  34. | risk gate and one-time confirm token | in the server | |
  35. | the trade as a script | `trade_pipeline` prompt | skills |
  36. | `/crypto-*` commands, triggers by phrase, plugin install | | ✓ |
  37. ## The steps
  38. | step | MCP tool / CLI | what it does |
  39. |---|---|---|
  40. | `crypto-scanner` | `scan` | Top perps by 24h volume: breakout of the session's opening range, RSI extremes. |
  41. | `crypto-derivs` | `derivs` | Funding now and 7-day average, open interest change, perp/spot basis, crowded-side flags. |
  42. | `crypto-entry` | `entry_check` | Waiting / triggered / expired, on closed bars only. |
  43. | `crypto-exit` | `exit_plan` | Stop (range-mid, range, ATR, price), target in R, flat-by time. |
  44. | `crypto-timemachine` | `timemachine` | 10,000 replays of the rest of the session from the coin's own bars + the same rule on every past session. |
  45. | `crypto-size` | `size` | Size from risk with fees, margin, liquidation estimate, funding cost. Places nothing. |
  46. | `crypto-risk` | `risk_check` | PASS / BLOCK against your limits. |
  47. | `crypto-broker` | `execute`, `confirm`, `flatten`, `positions`, `reconcile` | The only step that sends anything. |
  48. | | `settings` | Mode, exchange, account, limits, session — shown, and changed when you ask. |
  49. Crypto trades 24/7, so the "session" is yours: `session.start` (00:00 UTC by default), `range_minutes`,
  50. `entry_until`, `flat_by` — ask the assistant to change them, or `bytx-trader settings session.start=13:30`. Everything
  51. lands in `~/bytx-trader` (a project's own `crypto/` folder if it has one; `BYTX_TRADER_HOME` overrides) and each step
  52. reads what the last one wrote.
  53. ## An example: BTC on Binance, November 18 2026, real candles
  54. 1. **scan** at 01:05 UTC: BTC broke its first-hour range (64,673.5–64,976.3) to the downside; the 01:00 bar closed at
  55. 64,588.5, 0.131 % below.
  56. 2. **entry_check**: triggered, short.
  57. 3. **exit_plan** `--stop range-mid --target-r 2`: stop 64,824.9 (0.366 % away), target 64,115.7, flat by 23:55 UTC.
  58. 4. **timemachine**: 10,000 replays from the last 30 sessions (seed 19): target first 37.6 %, stop first 62.4 %. The same
  59. rule on those 30 sessions: fired 30 times, 9 targets, 21 stops. Expectancy before fees +0.13R simulated, −0.10R
  60. historical. Verdict: close to a coin flip — that is the point of looking before you risk a dollar.
  61. 5. **size** with 10 USDT at risk, 5x: ≈0.033 BTC, ≈2,131 USDT notional, margin ≈426, loss at the stop ≈9.94 USDT with fees.
  62. 6. **risk_check**: PASS.
  63. 7. **execute** shows the ticket and returns a one-time token; you answer yes; **confirm** sends it to the paper account.
  64. `tests/` reproduce these numbers offline from the candles in `tests/fixtures/`.
  65. ## Modes and the gates
  66. | mode | how | keys |
  67. |---|---|---|
  68. | **paper** (default) | live order book, virtual balance `account_usdt`, real taker fees | none |
  69. | **demo** | "switch to demo" (`settings`): the exchange's demo/testnet | `BYTX_API_KEY`, `BYTX_SECRET` (`BYTX_PASSWORD` for OKX, KuCoin, Bitget; `BYTX_WALLET_ADDRESS`, `BYTX_PRIVATE_KEY` for Hyperliquid) in the server's environment |
  70. | **real** | not sent by this package: real orders go through the hosted [BYTtrade](https://byttrade.com) MCP | kept by BYTtrade |
  71. Every order, in every mode, passes three gates, enforced in the code:
  72. 1. the risk check passed **this exact ticket** today (fingerprint);
  73. 2. `execute` sends nothing — it returns the ticket and a one-time token (5 min); `confirm` takes the token and **your
  74. reply word for word**, and anything but a plain yes cancels; the risk check runs again;
  75. 3. your client's own approval prompt for `confirm`.
  76. The client order id comes from the ticket, so if the exchange times out the order is found by that id with
  77. `reconcile` — it is never sent twice. Getting out (`flatten`) is never blocked by daily limits.
  78. ## Updates
  79. Started with `uvx` as above, the server picks up the newest `bytx-trader` and the newest compatible `bytx` every time
  80. your assistant starts it: fixes and new exchange features arrive with no action on your side. `bytx-trader` accepts
  81. `bytx` within one series (`>=0.2.2,<0.3`), so a breaking `bytx` release never arrives on its own: it comes with a
  82. `bytx-trader` release that was tested against it. Installed with `pip`, the server checks PyPI once a day and tells you
  83. in its first answer when an update is out (`BYTX_TRADER_NO_UPDATE_CHECK=1` turns that off). Claude skills installed as
  84. a plugin update with the marketplace (`/plugin`).
  85. ## Development
  86. ```bash
  87. pip install -e ".[test]" && pytest
  88. ```
  89. Tests are offline: real candles in `tests/fixtures/`, orders on `bytx.testing` paper accounts. CI runs them on every
  90. push and daily against the newest `bytx`; before a `bytx` release, run them against the release candidate:
  91. `gh workflow run tests.yml -R byttrade/bytx-skills -f bytx=git+https://github.com/byttrade/bytx@<branch>`.
  92. ## Fine print
  93. **Not financial advice.** Most people who trade actively lose money; leverage makes it faster. A stop is a plan, not
  94. a guarantee: gaps, slippage and auto-deleveraging can fill it far away, and liquidation can come first if leverage is
  95. high. Funding is charged every period while a position is open. The time machine is a simulation from the last few
  96. weeks, not a prediction. Paper trading simplifies margin and liquidation and does not watch your stop between runs.
  97. Keys live in environment variables, never in the chat. Orders are sent only by bytx and bytx-trader as released: an
  98. edited install is refused (the bytx license does not permit modified copies; `uv cache clean` restores it).
  99. MIT. Built on [bytx](https://pypi.org/project/bytx/) (BYTtrade Source-Available License, installed from PyPI, not
  100. copied here). No-code bots, backtests and trade confirmations in Telegram — at [byttrade.com](https://byttrade.com).
  101. <sub>**All risk is yours.** bytx-skills is a tool, provided as is, without any warranty. You alone decide whether and
  102. how to use it, and you alone bear every loss, missed profit or other consequence, including those caused by errors in
  103. the software, the data, an exchange or an AI assistant. Test it yourself — on paper, then on an exchange demo account —
  104. and only once you are satisfied that it works for you, use it with real money, in amounts you can afford to lose.
  105. The authors and BYTtrade are not liable for any trading results.</sub>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.