AGENT SKILL

paradex-structure-analyst

Draws the payoff for a Paradex options structure the user is CONSIDERING, not one they have traded. Invoked as `/paradex_structure_analyst structure <product> <n> legs`, which the Paradex order builder sends from its Analyze with DT button, and the legs arrive as hidden context. Draws the chart and says what the structure costs, in one pass, with no venue reads. Use when the user asks about a structure in the order builder. A trade that already filled belongs to paradex-trade-analyst. Paradigm RFQ blocks belong to paradigm-block-analyst, and a block from the Option Monitor to paradex-block-analyst.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 0
Forks
0

01 前言 Front Matter

name
paradex-structure-analyst
metadata
{ "author": "tradeparadigm", "version": "1.0" }
description
Draws the payoff for a Paradex options structure the user is CONSIDERING, not one they have traded. Invoked as `/paradex_structure_analyst structure <product> <n> legs`, which the Paradex order builder sends from its Analyze with DT button, and the legs arrive as hidden context. Draws the chart and says what the structure costs, in one pass, with no venue reads. Use when the user asks about a structure in the order builder. A trade that already filled belongs to paradex-trade-analyst. Paradigm RFQ blocks belong to paradigm-block-analyst, and a block from the Option Monitor to paradex-block-analyst.
compatibility
Reads nothing. Everything it needs arrives in the message, so it needs no credential, no helper and no network.

03 SKILL.md 正文

Paradex structure analyst

Draws the payoff for a structure the order builder is holding.

The first answer is a take, not a drawing

The user is looking at this payoff already. Drawing it back is worthless. Tell them what the trade IS and whether it is any good.

Answer in ONE pass: no commands, no files, no API calls, no other skill. Everything below is in the message.

Four or five lines, no headings, no chart:

  • What it is betting on, in plain words, and how far spot has to travel. Breakeven minus spot, as a number and a percentage.
  • What it costs if nothing happens. The premium is the whole loss, and with a near expiry most of it goes in hours rather than days — say so.
  • The one thing that would change your mind about it: the expiry is tomorrow, the strike is far, the premium is a large share of the move you need.
  • End with a concrete alternative, named with its strikes. Not "consider a spread" — "sell the 85000 against it and you halve the debit, capping you at 1,000".

Say what you would do. The user asked an expert, not a calculator.

What arrives

/paradex_structure_analyst structure <product> <n> legs. The visible line is a label. The structure is in the hidden context as JSON: each leg's optionType, side, strike, size, price (the live mark, not a fill), expiry and symbol, plus the underlying's spot and nearby_strikes, which are priced and ready to use. An amount arrives too when the user has set one in the builder: it scales the whole structure, and each leg's size stays per unit.

symbol is the market the order builder already resolved. Pass it through when you draw. A leg the builder could not name arrives without the field.

Never state a max loss, a breakeven or a max profit as a number the chart will also show, unless you are naming the breakeven to make a point about the distance to it.

Changing the trade

THIS is where the chart belongs. A structure different from the one on screen is worth drawing; the one already on screen is not.

So when the user asks for a change, or takes up the alternative you offered, reply with two lines on what the change buys them and end the message with the chart. Build it from nearby_strikes, which are already priced, and still run no commands.

Only if the strike you want is missing from nearby_strikes may you make one paradex__paradex_market_summaries(market_ids: ["<symbol>"]) call. If that fails, draw at your own estimate and say in one line that the price is an estimate.

The chart is the last thing in the message, written as this object:

{
  "id": "payoff-1",
  "layout": "stack",
  "children": [
    {
      "component": "options_payoff",
      "props": {
        "product": "BTC",
        "spot": 83356.2,
        "legs": [
          {"optionType": "CALL", "side": "BUY", "strike": 84000,
           "size": 1, "price": 391.58,
           "symbol": "BTC-USD-2OCT26-84000-C"},
          {"optionType": "CALL", "side": "SELL", "strike": 85000,
           "size": 1, "price": 180.59,
           "symbol": "BTC-USD-2OCT26-85000-C"}
        ]
      }
    }
  ]
}

The terminal renders the outermost {...} of a message when it carries layout and children, keeping the prose above as the text of the bubble. An object without both keys shows as raw JSON, which is what a bare {"mode": ..., "component": ..., "props": ...} does.

Put amount in props exactly as the context carried it, and leave it out when the context has none; never fold it into the legs' sizes, and never send 1 in its place.

Send every leg of the WHOLE structure, not just the one you added, and pass each symbol through as a string or leave the field out — never null, which is refused by the renderer and costs the chart. The chart works out the max loss, the breakeven and the max profit, so never write those yourself.

Never place an order, and never tell the user you have changed anything in their builder. Loading the structure is their click.

If the user asks for more

Only then read the venue. They can ask for the book, the greeks or how the price compares, and that is a second message, not part of this one.

04 同仓库更多 Skills

tradeparadigm
tradeparadigm/dt-apps

example-api

A skill body that exists so the fixture is a complete app. It teaches nothing and is never published.

★ 0
tradeparadigm
tradeparadigm/dt-apps

telegram-bot

Send messages, photos and files to Telegram through the user's own bot, using a bot token held by the DIME credential proxy. Covers finding the chats the bot can reach, posting to a private chat, group or channel, editing and deleting what it sent, and sending from a data feed. Use for ANY request to message, notify or alert the user on Telegram, "send this to my Telegram", "post alerts to my channel", or a 403 from the credential proxy on api.telegram.org.

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-rfq-trader

Trigger institutional block trades via Paradigm's DRFQv2 flow. The workflow is venue-agnostic — resolve instruments, build the RFQ / order payload, benchmark, run a confirmation gate, submit, verify settlement. Per-venue specifics (fair-value sources, naming conventions, edge syntax, settlement checks) live in references/venues.md. In scope today: PRDX (Paradex, primary focus) and DBT (Deribit). Adding more DRFQv2 venues is a references/venues.md edit, not a skill-body change. Covers takers (build, benchmark, cross) and makers (poll, price, manage). Every state-changing action goes through an explicit confirmation gate. Needs both Paradigm credentials enrolled. Use when the user asks to "send a Paradigm block RFQ", "block-trade X BTC", "send a BTC straddle on Paradex / Deribit", "quote rfq_X", "hit the best bid", "cancel rfq_X". Does NOT cover pricing a structure without trading (its legs' current marks are paradigm-data-discovery's), small central-order-book trades, post-trade analysis (paradigm-block-analyst), historical tape (paradigm-data-discovery).

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-options-recap

Options market recap for a requested or default window, invoked via /recap. Parses "/recap [asset] [options] [window]" (e.g. "/recap btc options 8h") and builds the fixed four-section recap — Snapshot, Biggest Print, Block Flow, Vol Surface — from bounded raw exchange venue files and source tapes, never from Dime hot files, read with the pod's AWS access. Use when the user types /recap or asks for a market recap, an options flow summary, "what happened in BTC options" or "last Xh of flow". A single question is not a recap: the biggest print across venues is paradigm-data-discovery's (paradigm-api reads only Paradigm's own tape), and the vol surface, one IV or one venue's data is paradigm-data-discovery's, as are dataset inventory, schema and historical lookups. The output format is fixed — always the same four sections in the same order.

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-data-discovery

Catalog and query launcher for raw market data available to Dime in s3://dt-exchange-venue-data, s3://dt-paradigm-data, and s3://dt-paradex-data, read with the pod's AWS access. Use for data inventory, coverage, schema and historical analysis, for current venue market data (marks, IV, greeks, OI, funding, spot) on Deribit, OKX, Bybit and Bullish, and for recent block trades when the user has no Paradigm credentials enrolled (with them, paradigm-api reads the live tape). Explains the per-venue raw files and lets the model choose the bounded reads needed for the question. Does not cover account state, positions, vaults, or order placement.

★ 0
tradeparadigm
tradeparadigm/dt-apps

paradigm-block-analyst

Cross-venue analysis of Paradigm RFQ block trades using live market data from Deribit, OKX, and Bybit. Invoked as `/analyze <rfq_id> <rfq description>`: resolves the rfq_id by searching the Paradigm trade tape via the paradigm-data-discovery skill (the daily execution partitions, keyed by RFQ_ID) for the cleared-block record, then fetches live marks, IVs, and greeks per venue, computes net greeks for multi-leg structures, benchmarks the fill vs mark, reports how much of the structure traded over 24h / 7d / 30d and where else it printed, reads whether the flow moved the vol surface, and outputs a concise analysis. Use when the user runs `/analyze <rfq_id> ...`, pastes a Paradigm block trade JSON, or asks to analyze, benchmark, or get market color on a Paradigm RFQ execution. Covers outright calls/puts (CL/PL), strangles (SN), straddles (ST), butterflies (BF), condors (CO), calendars (CA), risk reversals (RR), covered calls, and custom multi-leg combos (CM). Also handles perp combos. Reads the Paradigm trade tape from S3 with the pod's AWS access.

★ 0