[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D9P6Z86GS7C1GEDQAC2RN9":3,"skill-same:01M7D9P6Z86GS7C1GEDQAC2RN9":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7D9P6Z86GS7C1GEDQAC2RN9","paradex-structure-analyst",null,"Draws the payoff for a Paradex options structure the user is CONSIDERING, not one they have traded. Invoked as `\u002Fparadex_structure_analyst structure \u003Cproduct> \u003Cn> 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.","tradeparadigm\u002Fdt-apps","tradeparadigm","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F72768132?v=4","01M7D9KY0PDJW6NWY8P936YNEX","Paradigm","01M7D9KY1BYPTKX9MGQHZKW4BP",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Fparadex\u002Fskills\u002Fparadex-structure-analyst\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: paradex-structure-analyst\ndescription: >\n  Draws the payoff for a Paradex options structure the user is CONSIDERING,\n  not one they have traded. Invoked as `\u002Fparadex_structure_analyst structure\n  \u003Cproduct> \u003Cn> legs`, which the Paradex order builder sends from its Analyze\n  with DT button, and the legs arrive as hidden context. Draws the chart and\n  says what the structure costs, in one pass, with no venue reads. Use when\n  the user asks about a structure in the order builder. A trade that already\n  filled belongs to paradex-trade-analyst. Paradigm RFQ blocks belong to\n  paradigm-block-analyst, and a block from the Option Monitor to\n  paradex-block-analyst.\ncompatibility: >\n  Reads nothing. Everything it needs arrives in the message, so it needs no\n  credential, no helper and no network.\nmetadata:\n  author: tradeparadigm\n  version: \"1.0\"\n---\n\n# Paradex structure analyst\n\nDraws the payoff for a structure the order builder is holding.\n\n## The first answer is a take, not a drawing\n\nThe user is looking at this payoff already. Drawing it back is worthless.\nTell them what the trade IS and whether it is any good.\n\nAnswer in ONE pass: no commands, no files, no API calls, no other skill.\nEverything below is in the message.\n\nFour or five lines, no headings, no chart:\n\n- What it is betting on, in plain words, and how far spot has to travel.\n  Breakeven minus spot, as a number and a percentage.\n- What it costs if nothing happens. The premium is the whole loss, and with\n  a near expiry most of it goes in hours rather than days — say so.\n- The one thing that would change your mind about it: the expiry is tomorrow,\n  the strike is far, the premium is a large share of the move you need.\n- End with a concrete alternative, named with its strikes. Not \"consider a\n  spread\" — \"sell the 85000 against it and you halve the debit, capping you\n  at 1,000\".\n\nSay what you would do. The user asked an expert, not a calculator.\n\n## What arrives\n\n`\u002Fparadex_structure_analyst structure \u003Cproduct> \u003Cn> legs`. The visible line\nis a label. The structure is in the hidden context as JSON: each leg's\n`optionType`, `side`, `strike`, `size`, `price` (the live mark, not a fill),\n`expiry` and `symbol`, plus the underlying's `spot` and `nearby_strikes`,\nwhich are priced and ready to use. An `amount` arrives too when the user\nhas set one in the builder: it scales the whole structure, and each leg's\n`size` stays per unit.\n\n`symbol` is the market the order builder already resolved. Pass it through\nwhen you draw. A leg the builder could not name arrives without the field.\n\nNever state a max loss, a breakeven or a max profit as a number the chart\nwill also show, unless you are naming the breakeven to make a point about\nthe distance to it.\n\n## Changing the trade\n\nTHIS is where the chart belongs. A structure different from the one on screen\nis worth drawing; the one already on screen is not.\n\nSo when the user asks for a change, or takes up the alternative you offered,\nreply with two lines on what the change buys them and end the message with\nthe chart. Build it from `nearby_strikes`, which are already priced, and\nstill run no commands.\n\nOnly if the strike you want is missing from `nearby_strikes` may you make one\n`paradex__paradex_market_summaries(market_ids: [\"\u003Csymbol>\"])` call. If that fails, draw at your own\nestimate and say in one line that the price is an estimate.\n\nThe chart is the last thing in the message, written as this object:\n\n```json\n{\n  \"id\": \"payoff-1\",\n  \"layout\": \"stack\",\n  \"children\": [\n    {\n      \"component\": \"options_payoff\",\n      \"props\": {\n        \"product\": \"BTC\",\n        \"spot\": 83356.2,\n        \"legs\": [\n          {\"optionType\": \"CALL\", \"side\": \"BUY\", \"strike\": 84000,\n           \"size\": 1, \"price\": 391.58,\n           \"symbol\": \"BTC-USD-2OCT26-84000-C\"},\n          {\"optionType\": \"CALL\", \"side\": \"SELL\", \"strike\": 85000,\n           \"size\": 1, \"price\": 180.59,\n           \"symbol\": \"BTC-USD-2OCT26-85000-C\"}\n        ]\n      }\n    }\n  ]\n}\n```\n\nThe terminal renders the outermost `{...}` of a message when it carries\n`layout` and `children`, keeping the prose above as the text of the bubble.\nAn object without both keys shows as raw JSON, which is what a bare\n`{\"mode\": ..., \"component\": ..., \"props\": ...}` does.\n\nPut `amount` in `props` exactly as the context carried it, and leave it out\nwhen the context has none; never fold it into the legs' sizes, and never\nsend 1 in its place.\n\nSend every leg of the WHOLE structure, not just the one you added, and pass\neach `symbol` through as a string or leave the field out — never null, which\nis refused by the renderer and costs the chart. The chart works out the max\nloss, the breakeven and the max profit, so never write those yourself.\n\nNever place an order, and never tell the user you have changed anything in\ntheir builder. Loading the structure is their click.\n\n## If the user asks for more\n\nOnly then read the venue. They can ask for the book, the greeks or how the\nprice compares, and that is a second message, not part of this one.\n","# Paradex structure analyst\n\nDraws the payoff for a structure the order builder is holding.\n\n## The first answer is a take, not a drawing\n\nThe user is looking at this payoff already. Drawing it back is worthless.\nTell them what the trade IS and whether it is any good.\n\nAnswer in ONE pass: no commands, no files, no API calls, no other skill.\nEverything below is in the message.\n\nFour or five lines, no headings, no chart:\n\n- What it is betting on, in plain words, and how far spot has to travel.\n  Breakeven minus spot, as a number and a percentage.\n- What it costs if nothing happens. The premium is the whole loss, and with\n  a near expiry most of it goes in hours rather than days — say so.\n- The one thing that would change your mind about it: the expiry is tomorrow,\n  the strike is far, the premium is a large share of the move you need.\n- End with a concrete alternative, named with its strikes. Not \"consider a\n  spread\" — \"sell the 85000 against it and you halve the debit, capping you\n  at 1,000\".\n\nSay what you would do. The user asked an expert, not a calculator.\n\n## What arrives\n\n`\u002Fparadex_structure_analyst structure \u003Cproduct> \u003Cn> legs`. The visible line\nis a label. The structure is in the hidden context as JSON: each leg's\n`optionType`, `side`, `strike`, `size`, `price` (the live mark, not a fill),\n`expiry` and `symbol`, plus the underlying's `spot` and `nearby_strikes`,\nwhich are priced and ready to use. An `amount` arrives too when the user\nhas set one in the builder: it scales the whole structure, and each leg's\n`size` stays per unit.\n\n`symbol` is the market the order builder already resolved. Pass it through\nwhen you draw. A leg the builder could not name arrives without the field.\n\nNever state a max loss, a breakeven or a max profit as a number the chart\nwill also show, unless you are naming the breakeven to make a point about\nthe distance to it.\n\n## Changing the trade\n\nTHIS is where the chart belongs. A structure different from the one on screen\nis worth drawing; the one already on screen is not.\n\nSo when the user asks for a change, or takes up the alternative you offered,\nreply with two lines on what the change buys them and end the message with\nthe chart. Build it from `nearby_strikes`, which are already priced, and\nstill run no commands.\n\nOnly if the strike you want is missing from `nearby_strikes` may you make one\n`paradex__paradex_market_summaries(market_ids: [\"\u003Csymbol>\"])` call. If that fails, draw at your own\nestimate and say in one line that the price is an estimate.\n\nThe chart is the last thing in the message, written as this object:\n\n```json\n{\n  \"id\": \"payoff-1\",\n  \"layout\": \"stack\",\n  \"children\": [\n    {\n      \"component\": \"options_payoff\",\n      \"props\": {\n        \"product\": \"BTC\",\n        \"spot\": 83356.2,\n        \"legs\": [\n          {\"optionType\": \"CALL\", \"side\": \"BUY\", \"strike\": 84000,\n           \"size\": 1, \"price\": 391.58,\n           \"symbol\": \"BTC-USD-2OCT26-84000-C\"},\n          {\"optionType\": \"CALL\", \"side\": \"SELL\", \"strike\": 85000,\n           \"size\": 1, \"price\": 180.59,\n           \"symbol\": \"BTC-USD-2OCT26-85000-C\"}\n        ]\n      }\n    }\n  ]\n}\n```\n\nThe terminal renders the outermost `{...}` of a message when it carries\n`layout` and `children`, keeping the prose above as the text of the bubble.\nAn object without both keys shows as raw JSON, which is what a bare\n`{\"mode\": ..., \"component\": ..., \"props\": ...}` does.\n\nPut `amount` in `props` exactly as the context carried it, and leave it out\nwhen the context has none; never fold it into the legs' sizes, and never\nsend 1 in its place.\n\nSend every leg of the WHOLE structure, not just the one you added, and pass\neach `symbol` through as a string or leave the field out — never null, which\nis refused by the renderer and costs the chart. The chart works out the max\nloss, the breakeven and the max profit, so never write those yourself.\n\nNever place an order, and never tell the user you have changed anything in\ntheir builder. Loading the structure is their click.\n\n## If the user asks for more\n\nOnly then read the venue. They can ask for the book, the greeks or how the\nprice compares, and that is a second message, not part of this one.\n",{"name":5,"metadata":24,"description":26,"compatibility":27},{"author":9,"version":25},"1.0","Draws the payoff for a Paradex options structure the user is CONSIDERING, not one they have traded. Invoked as `\u002Fparadex_structure_analyst structure \u003Cproduct> \u003Cn> 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.\n","Reads nothing. Everything it needs arrives in the message, so it needs no credential, no helper and no network.\n","main","4befefc366f86a32c20711cf3798aaf13df1cd59","apps\u002Fparadex\u002Fskills\u002Fparadex-structure-analyst","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps","https:\u002F\u002Fgithub.com\u002Ftradeparadigm","https:\u002F\u002Fparadigm.co\u002F","2026-11-13 17:14:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add tradeparadigm\u002Fdt-apps --skill paradex-structure-analyst",{"tool":41,"command":42},"bunx","bunx skills add tradeparadigm\u002Fdt-apps --skill paradex-structure-analyst",{"tool":44,"command":45},"pnpm","pnpm dlx skills add tradeparadigm\u002Fdt-apps --skill paradex-structure-analyst","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Fparadex\u002Fskills\u002Fparadex-structure-analyst\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7D9RW0ZFXNH3MCGZE2B9WHY","example-api","A skill body that exists so the fixture is a complete app. It teaches nothing and is never published.","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fscripts\u002Ftestdata\u002Fapps\u002Fexample\u002Fskills\u002Fexample-api\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7D9RN7GJCJR5QA2ZCE4MPTH","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.","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Ftelegram\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D9R7K7RPTJ4T7DZRHXD156","paradigm-rfq-trader","Trigger institutional block trades via Paradigm's DRFQv2 flow. The workflow is venue-agnostic — resolve instruments, build the RFQ \u002F 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\u002Fvenues.md. In scope today: PRDX (Paradex, primary focus) and DBT (Deribit). Adding more DRFQv2 venues is a references\u002Fvenues.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 \u002F 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).","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Fparadigm\u002Fskills\u002Fparadigm-rfq-trader\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7D9QV6WFQDW717AXTW7GJKE","paradigm-options-recap","Options market recap for a requested or default window, invoked via \u002Frecap. Parses \"\u002Frecap [asset] [options] [window]\" (e.g. \"\u002Frecap 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 \u002Frecap 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.","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Fparadigm\u002Fskills\u002Fparadigm-options-recap\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7D9QJYMTHRTDVJFW3AC0HDN","paradigm-data-discovery","Catalog and query launcher for raw market data available to Dime in s3:\u002F\u002Fdt-exchange-venue-data, s3:\u002F\u002Fdt-paradigm-data, and s3:\u002F\u002Fdt-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.","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Fparadigm\u002Fskills\u002Fparadigm-data-discovery\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7D9Q3F60BDBMC8PEGH1VBZG","paradigm-block-analyst","Cross-venue analysis of Paradigm RFQ block trades using live market data from Deribit, OKX, and Bybit. Invoked as `\u002Fanalyze \u003Crfq_id> \u003Crfq 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 \u002F 7d \u002F 30d and where else it printed, reads whether the flow moved the vol surface, and outputs a concise analysis. Use when the user runs `\u002Fanalyze \u003Crfq_id> ...`, pastes a Paradigm block trade JSON, or asks to analyze, benchmark, or get market color on a Paradigm RFQ execution. Covers outright calls\u002Fputs (CL\u002FPL), 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.","https:\u002F\u002Fgithub.com\u002Ftradeparadigm\u002Fdt-apps\u002Fblob\u002Fmain\u002Fapps\u002Fparadigm\u002Fskills\u002Fparadigm-block-analyst\u002FSKILL.md",[],[]]