[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSQVS534KFZ3696DXV7DK2":3,"skill-same:01M6GSQVS534KFZ3696DXV7DK2":123},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6GSQVS534KFZ3696DXV7DK2","gate-exchange-trading-copilot",null,"Gate Trading Copilot L2. Use when the user wants to execute complex trades, margin borrowing, or query positions and open orders. Triggers on 'market buy', 'margin borrow', 'TradFi', 'Alpha', or spot-plus-futures combos. Requires Action Draft.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"gate exchange trading copilot","trading","gate","copilot","exchange","orders","2026","when","tradfi","borrowing","action","l2","triggers","spot","buy","positions","draft","query","Market","use","open","futures","alpha","2026-11-10 10:12:30",false,"---\nname: gate-exchange-trading-copilot\nversion: \"2026.3.23-1\"\nupdated: \"2026-03-23\"\ndescription: \"Gate Trading Copilot L2. Use when the user wants to execute complex trades, margin borrowing, or query positions and open orders. Triggers on 'market buy', 'margin borrow', 'TradFi', 'Alpha', or spot-plus-futures combos. Requires Action Draft.\"\n---\n\n# Gate Exchange Trading Copilot\n\nThis is an **L2 composite skill** for users who want a single skill to complete the full trading loop:\n\n`judge the opportunity -> control risk -> produce order draft -> explicit confirmation -> execute -> verify\u002Fmanage`\n\nIt is neither a pure research skill nor a pure execution skill. Its purpose is to provide a complete trading workflow inside one skill.\n\n## General Rules\n\n⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.\nDo NOT select or call any tool until all rules are read. These rules have the highest priority.\n→ Read [gate-runtime-rules.md](https:\u002F\u002Fgithub.com\u002Fgate\u002Fgate-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fgate-runtime-rules.md)\n- **Only call MCP tools explicitly listed in this skill.** Tools not documented here must NOT be called, even if they\n  exist in the MCP server.\n\nBefore calling any named MCP tool, verify that the concrete tool name exists in the current runtime tool list. If a helper tool is absent, disclose the mismatch, use only the nearest valid fallback combination, and do not overclaim unavailable coverage such as rankings, macro breadth, or automated fund-flow tracing.\n\nAlso validate that the returned payload is rich enough for the intended analytical claim. If a tool returns sparse metadata, empty structures, or requires missing disambiguation inputs, treat it as supporting context only rather than primary evidence.\n\nFor portability across Gate MCP runtimes, treat the documented surfaces as the baseline:\n\n- `info_*` -> Gate Info MCP\n- `news_feed_*` -> Gate News MCP\n- read-only `cex_spot_*` \u002F `cex_fx_*` market-data calls -> Gate public market MCP or a local combined Gate MCP runtime\n- private order \u002F account \u002F position `cex_*` calls -> authenticated Gate Exchange MCP or a local authenticated Gate MCP runtime\n\nDo not make `news_events_*` a required dependency in scenario design, because it is not part of the documented baseline news surface.\n\n## MCP Mode\n\n**Read and strictly follow** [`references\u002Fmcp.md`](.\u002Freferences\u002Fmcp.md), then execute this skill's copilot workflow.\n\n- `SKILL.md` keeps composite routing, trade lifecycle policy, and guardrails.\n- `references\u002Fmcp.md` is the authoritative MCP orchestration layer for cross-domain tool sequencing, execution gates, and degradation.\n\n---\n\nRead `references\u002Fscenarios.md` for:\n\n- representative user scenarios\n- representative prompt examples\n- expected tool-routing patterns\n\n## Authentication\n\n- API Key Required: Not always\n- Read-only analysis: public `info_*`, `news_feed_*`, and some public `cex_spot_*` \u002F `cex_fx_*` market-data calls may work without authentication, depending on runtime\n- Execution and private account actions: Yes, authenticated Exchange MCP tools with the required API key permissions are mandatory\n- Note: Do not block analysis-only use just because private execution tools are unavailable; only block when the requested action needs private trading\u002Faccount access.\n\n## Positioning\n\n- For users who want to trade without switching across multiple skills\n- Self-contained: can be installed alone and still understand both analysis and execution mapping\n- Supports **spot trading** and **USDT perpetual futures**\n- Supports post-trade **amend \u002F cancel \u002F close \u002F verification**\n\n## Suitable Scenarios\n\n### Suitable\n\n- The user already has a target asset and wants analysis before trading\n  - `Check whether BTC is worth buying now, then give me a spot order draft`\n  - `I want to long ETH, but check momentum, liquidation, and liquidity first`\n- The user is triggered by news, abnormal moves, or new listings and wants to trade after analysis\n  - `ETH just dumped. Explain why and tell me whether it is worth buying`\n  - `This newly listed coin looks interesting. Check the risk before giving me a starter trade plan`\n- The user already placed an order or opened a position and now wants management\n  - `Raise my unfilled buy order by 1%`\n  - `Close half of my BTC position`\n\n### Not Suitable\n\n- Pure market research with no trading goal\n- Options, Alpha trading, on-chain swap, DeFi execution, copy trading, wealth products\n- Fully automatic trading, skipping confirmation, bypassing compliance or risk controls\n\n## Capability Boundary\n\n### This skill can do\n\n1. Recognize whether the user wants:\n   - pre-trade judgment\n   - judgment plus execution\n   - order \u002F position management\n2. Dynamically combine analysis modules around one trade target:\n   - market\u002Fnews context\n   - single-coin analysis\n   - technical analysis\n   - liquidity\u002Fslippage\u002Fliquidation\u002Forder-book analysis\n   - token or contract risk check\n3. Produce a **Trading Brief**\n4. Produce an **Order Draft** when risk is acceptable\n5. Execute after explicit confirmation:\n   - spot buy\u002Fsell, conditional limit logic, amend\u002Fcancel\u002Fverification\n   - USDT perpetual open\u002Fclose\u002Freverse\u002Famend\u002Fcancel\n6. Continue after execution:\n   - fill verification\n   - position verification\n   - order \u002F position management\n\n### This skill cannot do\n\n1. Decide and trade automatically on behalf of the user\n2. Place orders without explicit confirmation\n3. Bypass compliance, risk, minimum order, or contract safety constraints\n4. Promise profit or present analysis as certainty\n5. Pretend to support unsupported products\n\n## Operating Principles\n\n### Principle 1: Work around the trading goal\n\nThis skill is built for trading closure, not broad research.\n\n- If the user only asks `How is the market?`\n  - a lightweight market scan is fine\n  - do not proactively move into order execution\n- If the user says `How is the market today? Give me one trade idea`\n  - a lightweight scan is allowed\n  - but the workflow must narrow down to **one asset + one market (spot or futures)** before entering execution\n\n### Principle 2: Judge first, execute second\n\nUnless the user only wants pure order\u002Fposition management, default to one round of pre-trade judgment before producing an order draft.\n\n### Principle 3: Use the minimum necessary analysis\n\nDo not run every module every time. Only call the modules needed for the current decision.\n\nRead `references\u002Frouting-and-analysis.md` for:\n\n- intent routing\n- analysis module selection by scenario\n- risk gating\n- module-to-MCP mapping and call patterns\n\n### Principle 4: Strong confirmation at execution layer\n\nAny real trading action must follow this order:\n\n1. Produce a `Trading Brief`\n2. Produce an `Order Draft`\n3. Wait for explicit confirmation in the immediately previous user turn\n4. Execute only after confirmation\n\nRead `references\u002Fexecution-and-guardrails.md` for:\n\n- spot and futures execution rules\n- execution MCP mapping\n- draft requirements\n- confirmation rules\n- hard and soft blocks\n\n## Overall Workflow\n\n### Step 0: Apply the shared runtime rules first\n\nBefore analysis or execution:\n\n- read and follow [gate-runtime-rules.md](https:\u002F\u002Fgithub.com\u002Fgate\u002Fgate-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fgate-runtime-rules.md)\n- resolve any required runtime, update, or authorization gate before continuing\n- verify that the named tools you plan to call exist in the current runtime before relying on them\n\n### Step 1: Identify task mode\n\nClassify the user request into one of these modes:\n\n1. **Trade Decision**\n   - analyze first, then decide whether to trade\n2. **Trade Draft \u002F Execute**\n   - the user already wants to trade and wants analysis plus draft plus execution\n3. **Order \u002F Position Management**\n   - the user wants to manage an existing order or position\n\n### Step 2: Narrow down to one trade target\n\nBefore entering execution, try to make these explicit:\n\n- asset: BTC \u002F ETH \u002F SOL \u002F a new coin \u002F a futures contract\n- market: spot or USDT perpetual\n- direction: buy \u002F sell \u002F long \u002F short \u002F close\n\nIf information is still incomplete:\n\n- a lightweight market scan is allowed\n- but before producing an order draft, the workflow must narrow down to one asset and one market\n\n### Step 3: Build the pre-trade analysis package\n\nCall only the modules needed for this request:\n\n- market overview \u002F news briefing\n- listing \u002F exchange announcement context\n- single-coin analysis\n- technical analysis\n- event explanation\n- risk check\n- address tracing (only when the user really provides an address and wants tracing)\n- liquidity \u002F slippage \u002F momentum \u002F liquidation \u002F basis \u002F order-book analysis\n\n### Step 4: Produce a Trading Brief\n\n`Trading Brief` is the mandatory intermediate artifact before execution. It must include:\n\n1. what the user wants to do\n2. current market\u002Fasset judgment\n3. key risks\n4. whether the skill should continue to order drafting\n\nOnly three result states are allowed:\n\n- `GO` = safe enough to continue to order drafting\n- `CAUTION` = meaningful risk exists, but drafting may continue after warning\n- `BLOCK` = do not continue into order drafting\n\n### Step 5: Produce an Order Draft\n\nOnly produce an order draft when all of the following are true:\n\n- the user has real trading intent\n- the trade target is sufficiently clear\n- no hard block is triggered\n\n### Step 6: Wait for explicit confirmation\n\nIf the user does not provide a clear, immediate confirmation:\n\n- do not execute\n- remain in analysis \u002F draft \u002F query mode only\n\n### Step 7: Execute and verify\n\nAfter execution, always return:\n\n- whether execution succeeded\n- core fill\u002Forder\u002Fposition results\n- reasonable next actions, such as verify fill, amend, cancel, or close\n\n## Market Identification Rules\n\n### Default behavior\n\n- If the request clearly contains `long \u002F short \u002F leverage \u002F contract \u002F perp \u002F futures \u002F open \u002F close`\n  - route to **USDT perpetual futures**\n- If the request clearly contains `buy coin \u002F sell coin \u002F spot \u002F buy BTC \u002F sell ETH`\n  - route to **spot**\n- If the user says `buy BTC` without specifying market\n  - default to **spot**\n- If the user says `trade this move`\n  - ask whether they want spot or USDT perpetual futures\n\n## Recommended Output Rhythm\n\n### Before execution\n\n1. `Trading Brief`\n2. if allowed: `Order Draft`\n3. wait for confirmation\n\n### After execution\n\n1. `Execution Result`\n2. if needed: `Next Actions`\n\n## Special Rule for Order \u002F Position Management\n\nIf the user asks for:\n\n- amend order\n- cancel order\n- verify fill\n- close half\n- close all\n- reverse\n\nthen the skill does not need to rerun the full research chain, but it still must:\n\n- locate the correct target order or position\n- apply the corresponding execution rules\n- require strong confirmation for high-risk actions\n\n## Risk Policy\n\n### Hard blocks\n\nMust stop immediately if:\n\n- the user asks to skip confirmation\n- the user asks to bypass compliance or risk controls\n- the product is unsupported\n- the asset is not tradable\n- token security check shows a critical malicious risk\n\n### Soft blocks\n\nWarn but allow continuation if:\n\n- liquidity is poor\n- slippage is high\n- funding is extreme\n- crowding\u002Fliquidation risk is elevated\n- a major event just hit and direction is unstable\n- the coin is newly listed or still in price discovery\n\nFor soft blocks:\n\n- surface the warning clearly in `Trading Brief`\n- if the user still wants to continue, drafting is allowed\n- confirmation is still mandatory\n\n## Reading Order\n\n1. Read `references\u002Frouting-and-analysis.md`\n2. Read `references\u002Fexecution-and-guardrails.md`\n3. Execute only the modules needed for the current task; do not run the full stack by default\n","# Gate Exchange Trading Copilot\n\nThis is an **L2 composite skill** for users who want a single skill to complete the full trading loop:\n\n`judge the opportunity -> control risk -> produce order draft -> explicit confirmation -> execute -> verify\u002Fmanage`\n\nIt is neither a pure research skill nor a pure execution skill. Its purpose is to provide a complete trading workflow inside one skill.\n\n## General Rules\n\n⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding.\nDo NOT select or call any tool until all rules are read. These rules have the highest priority.\n→ Read [gate-runtime-rules.md](https:\u002F\u002Fgithub.com\u002Fgate\u002Fgate-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fgate-runtime-rules.md)\n- **Only call MCP tools explicitly listed in this skill.** Tools not documented here must NOT be called, even if they\n  exist in the MCP server.\n\nBefore calling any named MCP tool, verify that the concrete tool name exists in the current runtime tool list. If a helper tool is absent, disclose the mismatch, use only the nearest valid fallback combination, and do not overclaim unavailable coverage such as rankings, macro breadth, or automated fund-flow tracing.\n\nAlso validate that the returned payload is rich enough for the intended analytical claim. If a tool returns sparse metadata, empty structures, or requires missing disambiguation inputs, treat it as supporting context only rather than primary evidence.\n\nFor portability across Gate MCP runtimes, treat the documented surfaces as the baseline:\n\n- `info_*` -> Gate Info MCP\n- `news_feed_*` -> Gate News MCP\n- read-only `cex_spot_*` \u002F `cex_fx_*` market-data calls -> Gate public market MCP or a local combined Gate MCP runtime\n- private order \u002F account \u002F position `cex_*` calls -> authenticated Gate Exchange MCP or a local authenticated Gate MCP runtime\n\nDo not make `news_events_*` a required dependency in scenario design, because it is not part of the documented baseline news surface.\n\n## MCP Mode\n\n**Read and strictly follow** [`references\u002Fmcp.md`](.\u002Freferences\u002Fmcp.md), then execute this skill's copilot workflow.\n\n- `SKILL.md` keeps composite routing, trade lifecycle policy, and guardrails.\n- `references\u002Fmcp.md` is the authoritative MCP orchestration layer for cross-domain tool sequencing, execution gates, and degradation.\n\n---\n\nRead `references\u002Fscenarios.md` for:\n\n- representative user scenarios\n- representative prompt examples\n- expected tool-routing patterns\n\n## Authentication\n\n- API Key Required: Not always\n- Read-only analysis: public `info_*`, `news_feed_*`, and some public `cex_spot_*` \u002F `cex_fx_*` market-data calls may work without authentication, depending on runtime\n- Execution and private account actions: Yes, authenticated Exchange MCP tools with the required API key permissions are mandatory\n- Note: Do not block analysis-only use just because private execution tools are unavailable; only block when the requested action needs private trading\u002Faccount access.\n\n## Positioning\n\n- For users who want to trade without switching across multiple skills\n- Self-contained: can be installed alone and still understand both analysis and execution mapping\n- Supports **spot trading** and **USDT perpetual futures**\n- Supports post-trade **amend \u002F cancel \u002F close \u002F verification**\n\n## Suitable Scenarios\n\n### Suitable\n\n- The user already has a target asset and wants analysis before trading\n  - `Check whether BTC is worth buying now, then give me a spot order draft`\n  - `I want to long ETH, but check momentum, liquidation, and liquidity first`\n- The user is triggered by news, abnormal moves, or new listings and wants to trade after analysis\n  - `ETH just dumped. Explain why and tell me whether it is worth buying`\n  - `This newly listed coin looks interesting. Check the risk before giving me a starter trade plan`\n- The user already placed an order or opened a position and now wants management\n  - `Raise my unfilled buy order by 1%`\n  - `Close half of my BTC position`\n\n### Not Suitable\n\n- Pure market research with no trading goal\n- Options, Alpha trading, on-chain swap, DeFi execution, copy trading, wealth products\n- Fully automatic trading, skipping confirmation, bypassing compliance or risk controls\n\n## Capability Boundary\n\n### This skill can do\n\n1. Recognize whether the user wants:\n   - pre-trade judgment\n   - judgment plus execution\n   - order \u002F position management\n2. Dynamically combine analysis modules around one trade target:\n   - market\u002Fnews context\n   - single-coin analysis\n   - technical analysis\n   - liquidity\u002Fslippage\u002Fliquidation\u002Forder-book analysis\n   - token or contract risk check\n3. Produce a **Trading Brief**\n4. Produce an **Order Draft** when risk is acceptable\n5. Execute after explicit confirmation:\n   - spot buy\u002Fsell, conditional limit logic, amend\u002Fcancel\u002Fverification\n   - USDT perpetual open\u002Fclose\u002Freverse\u002Famend\u002Fcancel\n6. Continue after execution:\n   - fill verification\n   - position verification\n   - order \u002F position management\n\n### This skill cannot do\n\n1. Decide and trade automatically on behalf of the user\n2. Place orders without explicit confirmation\n3. Bypass compliance, risk, minimum order, or contract safety constraints\n4. Promise profit or present analysis as certainty\n5. Pretend to support unsupported products\n\n## Operating Principles\n\n### Principle 1: Work around the trading goal\n\nThis skill is built for trading closure, not broad research.\n\n- If the user only asks `How is the market?`\n  - a lightweight market scan is fine\n  - do not proactively move into order execution\n- If the user says `How is the market today? Give me one trade idea`\n  - a lightweight scan is allowed\n  - but the workflow must narrow down to **one asset + one market (spot or futures)** before entering execution\n\n### Principle 2: Judge first, execute second\n\nUnless the user only wants pure order\u002Fposition management, default to one round of pre-trade judgment before producing an order draft.\n\n### Principle 3: Use the minimum necessary analysis\n\nDo not run every module every time. Only call the modules needed for the current decision.\n\nRead `references\u002Frouting-and-analysis.md` for:\n\n- intent routing\n- analysis module selection by scenario\n- risk gating\n- module-to-MCP mapping and call patterns\n\n### Principle 4: Strong confirmation at execution layer\n\nAny real trading action must follow this order:\n\n1. Produce a `Trading Brief`\n2. Produce an `Order Draft`\n3. Wait for explicit confirmation in the immediately previous user turn\n4. Execute only after confirmation\n\nRead `references\u002Fexecution-and-guardrails.md` for:\n\n- spot and futures execution rules\n- execution MCP mapping\n- draft requirements\n- confirmation rules\n- hard and soft blocks\n\n## Overall Workflow\n\n### Step 0: Apply the shared runtime rules first\n\nBefore analysis or execution:\n\n- read and follow [gate-runtime-rules.md](https:\u002F\u002Fgithub.com\u002Fgate\u002Fgate-skills\u002Fblob\u002Fmaster\u002Fskills\u002Fgate-runtime-rules.md)\n- resolve any required runtime, update, or authorization gate before continuing\n- verify that the named tools you plan to call exist in the current runtime before relying on them\n\n### Step 1: Identify task mode\n\nClassify the user request into one of these modes:\n\n1. **Trade Decision**\n   - analyze first, then decide whether to trade\n2. **Trade Draft \u002F Execute**\n   - the user already wants to trade and wants analysis plus draft plus execution\n3. **Order \u002F Position Management**\n   - the user wants to manage an existing order or position\n\n### Step 2: Narrow down to one trade target\n\nBefore entering execution, try to make these explicit:\n\n- asset: BTC \u002F ETH \u002F SOL \u002F a new coin \u002F a futures contract\n- market: spot or USDT perpetual\n- direction: buy \u002F sell \u002F long \u002F short \u002F close\n\nIf information is still incomplete:\n\n- a lightweight market scan is allowed\n- but before producing an order draft, the workflow must narrow down to one asset and one market\n\n### Step 3: Build the pre-trade analysis package\n\nCall only the modules needed for this request:\n\n- market overview \u002F news briefing\n- listing \u002F exchange announcement context\n- single-coin analysis\n- technical analysis\n- event explanation\n- risk check\n- address tracing (only when the user really provides an address and wants tracing)\n- liquidity \u002F slippage \u002F momentum \u002F liquidation \u002F basis \u002F order-book analysis\n\n### Step 4: Produce a Trading Brief\n\n`Trading Brief` is the mandatory intermediate artifact before execution. It must include:\n\n1. what the user wants to do\n2. current market\u002Fasset judgment\n3. key risks\n4. whether the skill should continue to order drafting\n\nOnly three result states are allowed:\n\n- `GO` = safe enough to continue to order drafting\n- `CAUTION` = meaningful risk exists, but drafting may continue after warning\n- `BLOCK` = do not continue into order drafting\n\n### Step 5: Produce an Order Draft\n\nOnly produce an order draft when all of the following are true:\n\n- the user has real trading intent\n- the trade target is sufficiently clear\n- no hard block is triggered\n\n### Step 6: Wait for explicit confirmation\n\nIf the user does not provide a clear, immediate confirmation:\n\n- do not execute\n- remain in analysis \u002F draft \u002F query mode only\n\n### Step 7: Execute and verify\n\nAfter execution, always return:\n\n- whether execution succeeded\n- core fill\u002Forder\u002Fposition results\n- reasonable next actions, such as verify fill, amend, cancel, or close\n\n## Market Identification Rules\n\n### Default behavior\n\n- If the request clearly contains `long \u002F short \u002F leverage \u002F contract \u002F perp \u002F futures \u002F open \u002F close`\n  - route to **USDT perpetual futures**\n- If the request clearly contains `buy coin \u002F sell coin \u002F spot \u002F buy BTC \u002F sell ETH`\n  - route to **spot**\n- If the user says `buy BTC` without specifying market\n  - default to **spot**\n- If the user says `trade this move`\n  - ask whether they want spot or USDT perpetual futures\n\n## Recommended Output Rhythm\n\n### Before execution\n\n1. `Trading Brief`\n2. if allowed: `Order Draft`\n3. wait for confirmation\n\n### After execution\n\n1. `Execution Result`\n2. if needed: `Next Actions`\n\n## Special Rule for Order \u002F Position Management\n\nIf the user asks for:\n\n- amend order\n- cancel order\n- verify fill\n- close half\n- close all\n- reverse\n\nthen the skill does not need to rerun the full research chain, but it still must:\n\n- locate the correct target order or position\n- apply the corresponding execution rules\n- require strong confirmation for high-risk actions\n\n## Risk Policy\n\n### Hard blocks\n\nMust stop immediately if:\n\n- the user asks to skip confirmation\n- the user asks to bypass compliance or risk controls\n- the product is unsupported\n- the asset is not tradable\n- token security check shows a critical malicious risk\n\n### Soft blocks\n\nWarn but allow continuation if:\n\n- liquidity is poor\n- slippage is high\n- funding is extreme\n- crowding\u002Fliquidation risk is elevated\n- a major event just hit and direction is unstable\n- the coin is newly listed or still in price discovery\n\nFor soft blocks:\n\n- surface the warning clearly in `Trading Brief`\n- if the user still wants to continue, drafting is allowed\n- confirmation is still mandatory\n\n## Reading Order\n\n1. Read `references\u002Frouting-and-analysis.md`\n2. Read `references\u002Fexecution-and-guardrails.md`\n3. Execute only the modules needed for the current task; do not run the full stack by default\n",{"name":5,"updated":52,"version":53,"description":7},"2026-03-23","2026.3.23-1","main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fexchanges\u002Fgate-trading-copilot",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-15 02:28:10",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill gate-exchange-trading-copilot",{"tool":69,"command":70},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill gate-exchange-trading-copilot",{"tool":72,"command":73},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill gate-exchange-trading-copilot","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002FSKILL.md",true,[77,83,87,91,95,99,103,107,111,115,119],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"_meta.json","REFERENCE","参考文档",148,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002F_meta.json",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"CHANGELOG.md",3531,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002FCHANGELOG.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"README.md",6636,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002FREADME.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fexecution-and-guardrails.md",10638,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002Freferences\u002Fexecution-and-guardrails.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fmcp.md",3381,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002Freferences\u002Fmcp.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Frouting-and-analysis.md",15693,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002Freferences\u002Frouting-and-analysis.md",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fruntime-dependencies.md",3055,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002Freferences\u002Fruntime-dependencies.md",{"path":108,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fscenarios.md",6318,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002Freferences\u002Fscenarios.md",{"path":112,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":113,"sourceHtmlUrl":114},"skill-card.md",3194,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002Fskill-card.md",{"path":116,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":117,"sourceHtmlUrl":118},"SOURCE.md",360,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002FSOURCE.md",{"path":120,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":121,"sourceHtmlUrl":122},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-trading-copilot\u002FTRUST.auto.yaml",[124,134,142,150,158,166],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":133},"01M7DTKCERMV0RNX3HZJP4CZ26","troves","Deposit and withdraw from Troves DeFi yield vault strategies on Starknet. View available strategies, check positions, and manage vault deposits. Use this skill when the user mentions Troves, vault, yield vault, DeFi vault, strategy, yield farming, vault deposit, vault withdraw, earning yield through vaults, passive yield strategies, or wants to deposit into or withdraw from a yield strategy — even if they don't say \"Troves\" explicitly.","MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-troves\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-troves\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":133},"01M7DTK6CJSMGC8KCQHGNYFZBD","trade","Swap tokens on Starknet via Fibrous DEX aggregator. Supports per-provider selection (avnu, ekubo, or auto to race all). Use this skill when the user wants to swap, exchange, trade, convert, buy, or sell one token for another on Starknet. Also use when the user asks about token prices, exchange rates, DEX routing, best swap route, or wants to check how much they would receive for a given amount — even if they don't explicitly say \"swap\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-trade\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-trade\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":133},"01M7DTJZ6A0X4PAW3Y8W4J9K64","staking","Stake, unstake, claim, and compound rewards for STRK, WBTC, tBTC, SolvBTC, and LBTC on Starknet. View validators, pools, and staking positions. Use this skill when the user mentions staking, delegating, validators, staking pools, rewards, compounding, unstaking, earning yield, passive income on crypto, or wants to earn on their STRK or BTC tokens — even if they don't say \"stake\" explicitly.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-staking\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-staking\u002FSKILL.md",[],[],{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":154,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":133},"01M7DTJSDZJKCDMW7GHRF4BRH5","send","Send STRK, ETH, or any ERC-20 token to a Starknet address. Supports simulation (dry-run) before execution. Use this skill when the user wants to send, transfer, pay, tip, or move tokens to another wallet address on Starknet. Also trigger when the user mentions sending funds to someone, making a payment, transferring assets, or moving crypto to a specific address — even if they just say \"pay 10 STRK to 0x...\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-send\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-send\u002FSKILL.md",[],[],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":133},"01M7DTJG1E480D51ZQ7WKDQ26K","portfolio","View a comprehensive DeFi portfolio dashboard and optimize portfolio allocation via automated rebalancing. Use this skill when the user wants an overview, summary, dashboard, total value, net worth, portfolio rebalancing, target allocation, or wants to see all their DeFi positions across Starknet at once. Also trigger when the user asks \"what do I have\", \"show me everything\", \"how much am I worth\", \"my positions\", \"my investments\", \"rebalance my portfolio\", \"I want 50% ETH\", \"optimize my holdings\", or any request for a holistic view of their Starknet holdings — even if they don't explicitly say \"portfolio\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-portfolio\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-portfolio\u002FSKILL.md",[],[],{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":128,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":133},"01M7DTJ7M8TE9R2N36HFBZDGVD","multi-swap","Execute multiple token swaps in a single Starknet transaction via Fibrous (default). Supports per-provider selection (avnu, ekubo, or auto to race all). Supports 2-3 swap pairs bundled into one multicall. Use this skill when the user wants to swap multiple token pairs at once, do batch swaps, execute several trades simultaneously, perform parallel swaps, or do bulk trading in one transaction. Also trigger when the user mentions \"two swaps\", \"three swaps\", \"swap X and Y at the same time\", or wants to convert multiple tokens in a single call.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-multi-swap\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-multi-swap\u002FSKILL.md",[],[]]