Self-hosted AI trading terminal for Hyperliquid: chart read in, validated Freqtrade/Nautilus-Trader strategy out, deployed live.
# Add to your Claude Code skills
git clone https://github.com/Superior-Trade/trading-terminalGuides for using ai agents skills like trading-terminal.
See how trading-terminal compares with popular alternatives.
trading-terminal is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Superior-Trade. Self-hosted AI trading terminal for Hyperliquid: chart read in, validated Freqtrade/Nautilus-Trader strategy out, deployed live. It has 50 GitHub stars.
trading-terminal's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/Superior-Trade/trading-terminal" and add it to your Claude Code skills directory (see the Installation section above).
trading-terminal is primarily written in TypeScript. It is open-source under Superior-Trade on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh trading-terminal against similar tools.
No comments yet. Be the first to share your thoughts!
Unlocks once the catalog security scan passes (runs nightly).
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
An AI trading terminal for Hyperliquid. Sketch your read straight onto the chart; the agent turns it into a real setup with entry, stop and target, ranks more setups beside it, and writes the Freqtrade strategy that trades the one you pick — refusing the unsafe ones on the way.
Run it yourself, or use the hosted build at terminal.superior.trade.
You draw the path. It comes back with a plan, a rating, and a deploy button.
[!TIP] Have an agent instead of a mouse? The terminal is for humans. If you want your agent trading directly — no UI, no clone — hand it one line:
Read https://superior.trade/SKILL.md and register.Works from Claude Code, OpenClaw, Codex and Cursor. Pointing a coding agent at this repository instead? AGENTS.md.
npm run setup:charts).1. You draw a level and ask.
"HYPE keeps rejecting off this line. Is there a mean-reversion trade here on the 15m?"
2. The agent reads your actual chart — your drawings, the visible range, the indicators you have plotted, and a screenshot of it — and answers with a plan:
| Entry | 38.20 — close crossing back above the band |
| Stop | 36.90 (−3.4%) |
| Target | 41.05 (+7.5%) |
| Invalidation | 15m close below 36.50 |
3. You say deploy. It writes the strategy, and the validator reads it before anything else does:
def populate_entry_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame:
dataframe.loc[
(
(dataframe['volume'] > 0) & # no signals on dead candles
(dataframe['close'] < dataframe['bb_lower']) &
(dataframe['rsi'] < 40) &
(dataframe['close'] > dataframe['ema_50'])
),
'enter_long'
] = 1
4. It runs. Live PnL, an auto-stop timer if the edge is time-boxed, and an inbox that tells you when something happened.
The other half — what you have deployed, what state it is in, and the controls.
The hosted build at terminal.superior.trade is this repository with a login in front of it. Both talk to the same Superior Trade API and trade the same accounts, so the choice is about who runs the process, not about what you get.
Running your own copy means your keys stay on your machine and every prompt and safety rule is yours to change. It also means no login (see SECURITY.md), withdrawals that stop one hop short (see docs/withdrawals.md), and getting your own TradingView access before the chart will build.
The interesting part of this repo is not that a model writes Python. It is what happens between "the model wrote it" and "it is trading your funds".
Every generated strategy is parsed and checked before it can be submitted. A rejection is not an error you see — the complaints go back to the model, which rewrites the strategy, and the loop repeats until it passes. Some of what gets caught:
| The check | What it prevents |
|---|---|
No shift(-N) in populate_* |
Reading future candles. The backtest looks superb and live behaves nothing like it |
| Stops are leverage-scaled | A 3.7% price stop written raw at 10× is ten times tighter than intended. The bot churns fees until the balance is gone |
Entries gate on volume > 0 |
Signals firing on dead candles |
startup_candle_count ≥ 3× the longest lookback |
Indicators are NaN live, so the bot silently never trades — the pod stays healthy and nothing happens |
| TA-Lib tuples indexed by position | bollinger['upperband'] raises on every candle. One live strategy did this for ten hours while its entry condition was met seven times |
Most of these are scars: they exist because a strategy reached production without them. docs/strategy-pipeline.md has the full set and explains the repair loop.
| Chart | TradingView Advanced Charts (or the bundled Lightweight Charts preview), Hyperliquid + Lighter datafeeds, order-flow footprint, liquidation heatmap, tier-ranked indicators |
| Agent | Reads your drawings and a screenshot of the chart; draws back — levels, zones, trendlines, channels, fibs |
| Setups | Scan a chart for plans, or design one in conversation. Entry, stop, target, invalidation, confidence tier |
| Strategies | Freqtrade code generation, deterministic safety validation, automatic repair, historical backtests |
| Execution | Live deployments, bracket orders for one-shot plans, position sizing, leverage caps, time-boxed auto-stop |
| Funds | Deposit, transfer between accounts, consolidate idle wallets, withdraw |
| Self-hosted only | Embedded Postgres, no login, no telemetry unless you turn it on, every prompt editable |
Two keys. Nothing else to sign up for.
git clone https://github.com/Superior-Trade/trading-terminal.git
cd trading-terminal
npm install
cp .env.example .env.local # add the two keys below
npm run dev # → http://localhost:3200
| Where | |
|---|---|
SUPERIOR_TRADE_API_KEY |
Sign up at terminal.superior.trade → Account → API keys |
OPENROUTER_API_KEY |
openrouter.ai/keys |
No database to provision, no login screen. An embedded Postgres
writes to ./.data/ and migrates itself on first boot.
.env.example documents 38 variables. Those two are the only ones without a working
default.
[!NOTE] It starts on the preview chart. TradingView's Advanced Charts is free but not redistributable, so it is not in this repository and a fresh clone runs Lightweight Charts instead — Apache-2.0, bundled, nothing to request.
Everything works on it, including drawing your read: a small toolbar on the chart draws freehand brush strokes, trendlines, rays, horizontal levels, vertical lines, rectangles and fib retracements, and the agent reads them the same way it reads TradingView drawings. What the preview still lacks is text notes and indicator studies. To get those, request Advanced Charts at tradingview.com/advanced-charts (free, a day or two) and run
npm run setup:charts. The build tells you which chart it picked. The hosted build at terminal.superior.trade already runs the full TradingView chart, drawings and all. Full comparison: docs/charting-library.md.
This places real orders with real funds by design. The validator above catches the
mistakes we know about, not the ones we don't — so read what the agent writes before you
deploy it, and start on testnet (NEXT_PUBLIC_HL_NETWORK=testnet) or with an amount you
would shrug at.
A backtest is not a prediction, and neither is the agent's reasoning. Not investment advice, no promise of profit, and you are responsible for what you run.
| docs/architecture.md | How a sentence becomes a running bot |
| docs/strategy-pipeline.md | Generation, validation, repair, logging |
| docs/charting-library.md | Installing TradingView Advanced Charts |
| docs/withdrawals.md | How money gets out, and how far this repo takes it |
| docs/self-hosting.md | Configuration, databases, running it somewhere else |
npm run dev # dev server on :3200
npm test # unit tests
npm run test:e2e # 19 checks against a running server, nothing mocked
npm run check-types
npm run lint
npm run preview # render README.md the way GitHub will, images and all
npm run test:e2e drives the whole app — boot, database, the Superior Trade API, market
data, real model calls. It never spends money: deploying and withdrawi