Superior Trade Lighter
SkillCloud & infraUse when onboarding, funding, trading, or withdrawing on Lighter through Superior Trade — account bootstrap, CCTP deposits from a Superior wallet, immediate orders, withdrawals, proxying signed Lighter transactions, or deploying and monitoring a Lighter Nautilus strategy.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Superior Trade Lighter skill
What this skill tells your AI
The instructions your AI receives, as published by superior-trade/superior-skills in skills/lighter/SKILL.md and read by ahel’s review.
Use this skill for Lighter market discovery, Nautilus backtests and deployments, managed-wallet checks, and supported typed executions through Unified API.
Read ../../references/unified-runtime.md
before making any request. The OpenAPI contract, not older venue workflows,
defines which Lighter operations are available.
Base URL: https://api.superior.trade
Auth: x-api-key: $SUPERIOR_TRADE_API_KEY
Venue config: { "venue": "lighter", "instrument_id": "<SYMBOL>.LIGHTER" }
Unified API only
Read ../../references/unified-runtime.md
before onboarding, backtesting, deployment, or execution. Use GET /context/venues
and GET /runtime/frameworks first, then the Unified runtime endpoints. If the
contract does not expose the required Lighter operation, report it as
unavailable.
Robinhood Chain Variant
Use the separate lighter-robinhood skill and venue name for Robinhood Chain Lighter. Do not treat lighter-robinhood as an alias for this default lighter profile; it uses a different venue profile, chain id, deposit asset, and instrument suffix.
Safety Rules
- Never ask for private keys, seed phrases, API private keys, passwords, or wallet credentials.
- Never log, echo, store, or display secrets. The only credential an agent should use is
SUPERIOR_TRADE_API_KEY. - Never move funds or start live trading without explicit user confirmation.
- Never submit a Lighter order without explicit user confirmation of market, side, size, order type, and risk.
- Treat any contract-supported Lighter deposit or withdrawal as a real fund-moving action.
- Do not retry an ambiguous execution or withdrawal automatically. Read its durable status and report the persisted state.
- Do not claim managed-wallet funds are available on Lighter unless Unified API returns the required readiness and balance evidence.
- Do not claim Lighter readiness or balance without querying the API.
- If onboarding, CCTP funding, delayed withdrawal, or signed proxy submission is
absent from
GET /openapi.json, report it as unavailable.
Account readiness
Read the managed wallet with GET /wallet and venue support with
GET /context/venues. Do not infer a Lighter-specific account state machine
from generic wallet history. If Unified API does not return the readiness data
needed for a live deployment, report the deployment as unavailable rather than
reusing an older onboarding flow.
Reference files
Load on demand.
| Read | When |
|---|---|
references/api.md | You need Unified routing for market context, wallet readiness, backtests, deployments, or supported typed executions. |
references/deployment.md | You are creating, starting, stopping or monitoring a Lighter Nautilus deployment. |
Related Skills
- Use
superior-trade-authfirst when the user needs an API key. - Use
trade-thesisbefore deploying a new live strategy idea. - Use
hyperliquidfor Hyperliquid workflows. Lighter deployments use the same Unified runtime lifecycle with the Nautilus framework.
Signals
- GitHub stars
- 211
- Forks
- 9
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
lighter- Source
- github.com/superior-trade/superior-skills