agentleFS
EskyeeEskyee/agentbot-opensource/skills/nexus-trading-labs/SKILL.md

nexus

Skill17 starsChanged 5 months agoMITView on GitHub

Non-custodial perpetual DEX on Arbitrum. Use when user says buy, sell, trade, long, short, open position, close position, flip trade, set leverage, deposit USDC, withdraw funds, check balance, view positions, cancel order, copy a thesis, publish trade on-chain, check leaderboard, top traders, Rep Score, market intel, crypto news, funding rate, thesis, analyst feed, who's winning on Nexus.

10 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    ⛔ DO NOT skip this: No walletSig = 401 error on every authenticated endpoint.

    line 28
  2. Very specific:

    NEVER call trade.nexustradinglabs.com for API requests — that is the static frontend app.

    line 35
  3. Very specific:

    NEVER prepend /api/ or /api/v1/ to endpoint paths — there is no such prefix on this API.

    line 36
  4. Distinctive:

    NEVER construct URLs from relative paths — always use the full URL from the quick reference table.

    line 37
  5. Very specific:

    NEVER embed stopLoss / takeProfit in the /trade body — place them via /set-sl-tp after fill

    line 38
  6. Distinctive:

    NEVER store or log the Bankr API key — use it transiently per call, never persist

    line 39
  7. Distinctive:

    NEVER ask the user to run terminal commands, install packages, or sign messages manually

    line 40
  8. Very specific:

    NEVER use the Orderly CLI (@orderly.network/cli)

    line 41
  9. Very specific:

    NEVER re-call sign_message before every request — one signature per session is enough

    line 42
  10. Very specific:

    If response is { error: "wallet_not_registered" } → run Registration Flow (see references/trading.md).

    line 60

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Nexus Trading Labs — Agent Skill

⚠️ CRITICAL — READ THIS BEFORE ANYTHING ELSE

Every authenticated action requires a wallet signature. Get it once, reuse for the session.

Step 1 — request_additional_tools({ names: ["sign_message"] })
Step 2 — commit_to_tools({ keep: ["sign_message"] })
Step 3 — sign_message({ message: "nexus-trading-key-v1" }) → save as walletSig
         also capture walletAddress from the connected wallet

⛔ DO NOT skip this. No walletSig = 401 error on every authenticated endpoint. ⛔ DO NOT ask the user for a signature. You have sign_message — use it yourself.


⛔ FORBIDDEN

  • NEVER call trade.nexustradinglabs.com for API requests — that is the static frontend app. It returns 405 on all POSTs.
  • NEVER prepend /api/ or /api/v1/ to endpoint paths — there is no such prefix on this API.
  • NEVER construct URLs from relative paths — always use the full URL from the quick reference table.
  • NEVER embed stopLoss / takeProfit in the /trade body — place them via /set-sl-tp after fill
  • NEVER store or log the Bankr API key — use it transiently per call, never persist
  • NEVER ask the user to run terminal commands, install packages, or sign messages manually
  • NEVER use the Orderly CLI (@orderly.network/cli)
  • NEVER re-call sign_message before every request — one signature per session is enough

Trade (most common action)

POST https://og.nexustradinglabs.com/trade
{
  "symbol":      "PERP_BTC_USDC",   // or shorthand "BTC"
  "side":        "BUY",             // or "SELL"
  "notional":    50,                // USD size
  "leverage":    5,
  "walletSig":   "<from sign_message>",
  "walletAddress": "<connected wallet>"
}

If response is { error: "wallet_not_registered" } → run Registration Flow (see references/trading.md).

To attach SL/TP after fill: POST /set-sl-tp (see references/trading.md — never put SL/TP in /trade).


Quick Reference

⚠️ ALWAYS use the full URL: https://og.nexustradinglabs.com

ActionFull URLAuth
Place tradePOST https://og.nexustradinglabs.com/tradewalletSig
Close positionPOST https://og.nexustradinglabs.com/close-positionwalletSig
Attach SL/TPPOST https://og.nexustradinglabs.com/set-sl-tpwalletSig
Cancel orderPOST https://og.nexustradinglabs.com/cancelwalletSig
Order statusPOST https://og.nexustradinglabs.com/order-statuswalletSig
Order historyPOST https://og.nexustradinglabs.com/order-historywalletSig
PositionsPOST https://og.nexustradinglabs.com/positionswalletSig
BalancePOST https://og.nexustradinglabs.com/balancewalletSig
Set leveragePOST https://og.nexustradinglabs.com/set-leveragewalletSig
Deposit USDCPOST https://og.nexustradinglabs.com/proxy/bankr-depositBankr API key
Withdraw USDCPOST https://og.nexustradinglabs.com/proxy/bankr-withdrawBankr API key + walletSig
Settle PnLPOST https://og.nexustradinglabs.com/settle-pnlwalletSig
Register walletPOST https://og.nexustradinglabs.com/proxy/bankr-registerBankr API key
Publish thesis on-chainPOST https://og.nexustradinglabs.com/proxy/thesis-registerBankr API key
Mark priceGET https://og.nexustradinglabs.com/mark-price?symbol=BTCpublic
Funding rateGET https://og.nexustradinglabs.com/funding-rate?symbol=BTCpublic
24h statsGET https://og.nexustradinglabs.com/24h-stats?symbol=BTCpublic
Public feedGET https://og.nexustradinglabs.com/feedpublic
Trader labGET https://og.nexustradinglabs.com/lab/:walletpublic read
Trader profileGET https://og.nexustradinglabs.com/profile/:walletpublic read
Leaderboardderive from GET https://og.nexustradinglabs.com/feed + getTraderStats()public
Market intelGET https://api-evm.orderly.org/v1/public/futurespublic
Crypto newsrss2json proxy (see references/news.md)public

Load References As Needed

  • references/trading.md — full trade flow, registration, SL/TP, close, cancel, order-status, order-history, positions, leverage
  • references/deposit-withdraw.md — deposit USDC, withdraw, settle PnL, balance
  • references/feed-leaderboard.md — public feed, thesis copy flow, on-chain registry, Rep Score, leaderboard build, notifications, comments
  • references/market-data.md — mark price, funding rate, 24h stats, error codes, retry logic, rate limits, testnet
  • references/intel.md — market intelligence: pull live OI, funding rates, regime signals from Orderly public API
  • references/news.md — pull latest crypto/macro news via RSS feeds before framing a trade or answering market questions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.