[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSQD95FGD4J84C2FNFYHR6":3,"skill-same:01M6GSQD95FGD4J84C2FNFYHR6":119},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6GSQD95FGD4J84C2FNFYHR6","gate-news-briefing",null,"News briefing. Use this skill ONLY when the user's query is exclusively about recent news or headlines with no other analysis dimensions. Trigger phrases: what happened recently, today's highlights, crypto news, any new updates. If the query ALSO mentions coin analysis, risk check, technicals, or any other analysis dimension, use gate-info-research instead — it handles multi-dimension queries in a single unified report.","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-news-briefing\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],"gate news briefing","news briefing","briefing","gate","news","dimensions","updates","with","multi","trigger","info","research","query","crypto","queries","only","use","check","analysis","risk","2026-11-10 10:12:30",false,"---\nname: gate-news-briefing\nversion: \"2026.4.7-1\"\nupdated: \"2026-04-07\"\ndescription: \"News briefing. Use this skill ONLY when the user's query is exclusively about recent news or headlines with no other analysis dimensions. Trigger phrases: what happened recently, today's highlights, crypto news, any new updates. If the query ALSO mentions coin analysis, risk check, technicals, or any other analysis dimension, use gate-info-research instead — it handles multi-dimension queries in a single unified report.\"\nrequired_credentials: []\nrequired_env_vars: []\nrequired_permissions: []\n---\n\n# gate-news-briefing\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 `.\u002Freferences\u002Fgate-runtime-rules.md`\n→ Also read `.\u002Freferences\u002Finfo-news-runtime-rules.md` for gate-info \u002F gate-news shared rules (tool degradation, report standards, security, and output standards).\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\n> The crypto industry \"morning briefing\" Skill. The user asks what's been happening; the system calls 3 MCP Tools in parallel to fetch major events + trending news + social sentiment, then the LLM aggregates into a layered news briefing.\n\n**Trigger Scenarios**: User asks about recent\u002Ftoday's news, headlines, or what's been happening.\n\n---\n\n## MCP Dependencies\n\n### Required MCP Servers\n| MCP Server | Status |\n|------------|--------|\n| Gate-News | ✅ Required |\n\n### MCP Tools Used\n\n**Query Operations (Read-only)**\n\n- news_events_get_latest_events\n- news_feed_get_social_sentiment\n- news_feed_search_news\n\n### Authentication\n- API Key Required: No\n- Credentials Source: None; this skill uses read-only Gate Info \u002F Gate News MCP access only.\n\n### Installation Check\n- Required: Gate-News\n- Install: Use the local Gate MCP installation flow for the current host IDE before continuing.\n- Continue only after the required Gate MCP server is available in the current environment.\n\n## Routing Rules\n\n| User Intent | Keywords | Action |\n|-------------|----------|--------|\n| General news briefing | \"what happened recently\" \"today's headlines\" \"crypto news\" \"any new updates\" | Execute this Skill's full workflow |\n| Coin-specific news | \"any SOL news\" \"what's happening with BTC\" | Execute this Skill with `coin` parameter set to that coin |\n| Reason for a move | \"why did BTC crash\" \"what just happened\" | Route to `gate-news-eventexplain` |\n| Overall market conditions | \"how's the market\" | Route to `gate-info-marketoverview` |\n| Exchange announcements | \"any new listings on Binance\" \"new coins lately\" | Route to `gate-news-listing` |\n\n---\n\n## Execution Workflow\n\n### Step 0: Multi-Dimension Intent Check\n\nBefore executing this Skill, check if the user's query involves multiple analysis dimensions:\n\n- If the query is exclusively about recent news or headlines, proceed with this Skill.\n- If the query **also** mentions coin analysis, risk check, technicals, fundamentals, or any other analysis dimension beyond news, route to `gate-info-research` — it handles multi-dimension queries with unified tool deduplication and coherent report aggregation.\n\n### Step 1: Intent Recognition & Parameter Extraction\n\nExtract from user input:\n- `coin` (optional): Whether a specific coin is targeted, e.g., \"SOL news\" → coin=SOL\n- `time_range`: Time window (default: 24h; if user says \"this week\" → 7d)\n- `topic` (optional): Whether focused on a specific topic (e.g., \"regulation\", \"ETF\", \"DeFi\")\n\n### Step 2: Call 3 MCP Tools in Parallel\n\n**General Briefing Mode** (no specific coin):\n\n| Step | MCP Tool | Parameters | Retrieved Data | Parallel |\n|------|----------|------------|----------------|----------|\n| 1a | `news_events_get_latest_events` | `time_range={time_range}, limit=10` | Major event list (with impact rating) | Yes |\n| 1b | `news_feed_search_news` | `sort_by=\"importance\", limit=10, lang=\"en\"` | Top news ranked by importance | Yes |\n| 1c | `news_feed_get_social_sentiment` | (no specific coin) | Market-wide social sentiment overview | Yes |\n\n**Coin-Specific Mode** (user specified a coin):\n\n| Step | MCP Tool | Parameters | Retrieved Data | Parallel |\n|------|----------|------------|----------------|----------|\n| 1a | `news_events_get_latest_events` | `coin={coin}, time_range={time_range}, limit=10` | Events related to that coin | Yes |\n| 1b | `news_feed_search_news` | `coin={coin}, sort_by=\"importance\", limit=10` | News related to that coin | Yes |\n| 1c | `news_feed_get_social_sentiment` | `coin={coin}` | Social sentiment for that coin | Yes |\n\n### Step 3: LLM Aggregation\n\nThe LLM must:\n1. De-duplicate events and news (the same event may appear in both feeds)\n2. Rank by impact\u002Fimportance\n3. Categorize (Regulation, Projects, Market, Technology, etc.)\n4. Combine with social sentiment to identify market focus areas\n\n### Step 4: Output Structured Briefing\n\n---\n\n## Report Template\n\n```markdown\n## Crypto Industry News Briefing\n\n> Time range: Past {time_range} | Generated: {timestamp}\n\n### ? Major Events\n\n{Top 1-3 events by impact, each containing:}\n\n**1. {event_title}**\n- Time: {event_time}\n- Impact: {Market\u002Findustry impact assessment}\n- Involved: {Related coins\u002Fprojects\u002Finstitutions}\n- Details: {2-3 sentence summary}\n\n**2. {event_title}**\n- ...\n\n---\n\n### ? Trending News\n\n{Grouped by category, 2-5 items per category:}\n\n**Regulation & Policy**\n1. {title} — {source} ({time})\n   {One-sentence summary}\n2. ...\n\n**Projects & Technology**\n1. {title} — {source} ({time})\n   {One-sentence summary}\n2. ...\n\n**Market & Trading**\n1. {title} — {source} ({time})\n   {One-sentence summary}\n2. ...\n\n**DeFi \u002F NFT \u002F GameFi** (if applicable)\n1. ...\n\n---\n\n### ? Social Sentiment\n\n| Metric | Status |\n|--------|--------|\n| Overall Sentiment | {Bullish\u002FBearish\u002FNeutral} |\n| Discussion Volume | {High\u002FMedium\u002FLow} |\n| Trending Topics | {topic1}, {topic2}, {topic3} |\n| KOL Focus | {focus description} |\n\n**Top 5 Coins by Discussion Volume** (if data available)\n\n| Rank | Coin | Volume Change | Sentiment |\n|------|------|--------------|-----------|\n| 1 | {coin} | +{change}% | {Bullish\u002FBearish} |\n| 2 | ... | ... | ... |\n\n---\n\n### ? Worth Watching\n\n{LLM distills 2-3 noteworthy points from news and sentiment:}\n- {Point 1}\n- {Point 2}\n- {Point 3}\n\n> The above is a news summary and does not constitute investment advice.\n```\n\n### Coin-Specific Mode Template\n\n```markdown\n## {symbol} News Briefing\n\n> Time range: Past {time_range} | Generated: {timestamp}\n\n### Recent Key Events\n\n1. {event} — {time}\n   {details}\n2. ...\n\n### Related News\n\n1. [{title}]({url}) — {source} ({time})\n   {summary}\n2. ...\n\n### Social Sentiment\n\n- Discussion Volume: {High\u002FMedium\u002FLow} (vs 7-day average: {change}%)\n- Sentiment Bias: {Bullish\u002FBearish\u002FNeutral}\n- KOL Views: {Summary of key KOL opinions}\n\n### Summary\n\n{1-2 sentence summary of the coin's recent news landscape}\n```\n\n---\n\n## De-duplication & Ranking Logic\n\n| Rule | Description |\n|------|-------------|\n| Event-News de-duplication | If an event title closely matches a news headline (similarity > 80%), merge into one entry — events take priority |\n| Importance ranking | Events ranked by impact rating; news ranked by `importance` field |\n| Time ordering | At equal importance, reverse chronological (newest first) |\n| Categorization | News auto-categorized: Regulation & Policy \u002F Projects & Technology \u002F Market & Trading \u002F DeFi \u002F Other |\n\n---\n\n## Error Handling\n\n| Error Type | Handling |\n|------------|----------|\n| `news_events_get_latest_events` fails | Skip \"Major Events\" section; show news only |\n| `news_feed_search_news` fails | Show events only; note \"News feed temporarily unavailable\" |\n| `news_feed_get_social_sentiment` fails | Skip \"Social Sentiment\" section |\n| All Tools fail | Return error message; suggest the user try again later |\n| Too few news items (\u003C 3) | Expand time range (e.g., 24h → 48h) and note the change |\n\n---\n\n## Cross-Skill Routing\n\n| User Follow-up Intent | Route To |\n|-----------------------|----------|\n| \"Why did XX pump\u002Fdump?\" | `gate-news-eventexplain` |\n| \"Analyze XX for me\" | `gate-info-coinanalysis` |\n| \"How's the overall market?\" | `gate-info-marketoverview` |\n| \"Any new listings on Binance?\" | `gate-news-listing` |\n| \"Tell me more about ETF\" | Deep search via `news_feed_search_news(query=\"ETF\")` |\n\n---\n\n## Safety Rules\n\n1. **Source attribution**: Every news item must include the source (media name) and time\n2. **No interpretive speculation**: News summaries must remain objective — no subjective extrapolation\n3. **No fabricated news**: If data is insufficient, reduce the number of items rather than fabricate content\n4. **Neutral handling of sensitive topics**: Maintain neutral tone when covering regulation, politics, or other sensitive subjects\n5. **Timeliness labeling**: Clearly label the time range covered by the data\n","# gate-news-briefing\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 `.\u002Freferences\u002Fgate-runtime-rules.md`\n→ Also read `.\u002Freferences\u002Finfo-news-runtime-rules.md` for gate-info \u002F gate-news shared rules (tool degradation, report standards, security, and output standards).\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\n> The crypto industry \"morning briefing\" Skill. The user asks what's been happening; the system calls 3 MCP Tools in parallel to fetch major events + trending news + social sentiment, then the LLM aggregates into a layered news briefing.\n\n**Trigger Scenarios**: User asks about recent\u002Ftoday's news, headlines, or what's been happening.\n\n---\n\n## MCP Dependencies\n\n### Required MCP Servers\n| MCP Server | Status |\n|------------|--------|\n| Gate-News | ✅ Required |\n\n### MCP Tools Used\n\n**Query Operations (Read-only)**\n\n- news_events_get_latest_events\n- news_feed_get_social_sentiment\n- news_feed_search_news\n\n### Authentication\n- API Key Required: No\n- Credentials Source: None; this skill uses read-only Gate Info \u002F Gate News MCP access only.\n\n### Installation Check\n- Required: Gate-News\n- Install: Use the local Gate MCP installation flow for the current host IDE before continuing.\n- Continue only after the required Gate MCP server is available in the current environment.\n\n## Routing Rules\n\n| User Intent | Keywords | Action |\n|-------------|----------|--------|\n| General news briefing | \"what happened recently\" \"today's headlines\" \"crypto news\" \"any new updates\" | Execute this Skill's full workflow |\n| Coin-specific news | \"any SOL news\" \"what's happening with BTC\" | Execute this Skill with `coin` parameter set to that coin |\n| Reason for a move | \"why did BTC crash\" \"what just happened\" | Route to `gate-news-eventexplain` |\n| Overall market conditions | \"how's the market\" | Route to `gate-info-marketoverview` |\n| Exchange announcements | \"any new listings on Binance\" \"new coins lately\" | Route to `gate-news-listing` |\n\n---\n\n## Execution Workflow\n\n### Step 0: Multi-Dimension Intent Check\n\nBefore executing this Skill, check if the user's query involves multiple analysis dimensions:\n\n- If the query is exclusively about recent news or headlines, proceed with this Skill.\n- If the query **also** mentions coin analysis, risk check, technicals, fundamentals, or any other analysis dimension beyond news, route to `gate-info-research` — it handles multi-dimension queries with unified tool deduplication and coherent report aggregation.\n\n### Step 1: Intent Recognition & Parameter Extraction\n\nExtract from user input:\n- `coin` (optional): Whether a specific coin is targeted, e.g., \"SOL news\" → coin=SOL\n- `time_range`: Time window (default: 24h; if user says \"this week\" → 7d)\n- `topic` (optional): Whether focused on a specific topic (e.g., \"regulation\", \"ETF\", \"DeFi\")\n\n### Step 2: Call 3 MCP Tools in Parallel\n\n**General Briefing Mode** (no specific coin):\n\n| Step | MCP Tool | Parameters | Retrieved Data | Parallel |\n|------|----------|------------|----------------|----------|\n| 1a | `news_events_get_latest_events` | `time_range={time_range}, limit=10` | Major event list (with impact rating) | Yes |\n| 1b | `news_feed_search_news` | `sort_by=\"importance\", limit=10, lang=\"en\"` | Top news ranked by importance | Yes |\n| 1c | `news_feed_get_social_sentiment` | (no specific coin) | Market-wide social sentiment overview | Yes |\n\n**Coin-Specific Mode** (user specified a coin):\n\n| Step | MCP Tool | Parameters | Retrieved Data | Parallel |\n|------|----------|------------|----------------|----------|\n| 1a | `news_events_get_latest_events` | `coin={coin}, time_range={time_range}, limit=10` | Events related to that coin | Yes |\n| 1b | `news_feed_search_news` | `coin={coin}, sort_by=\"importance\", limit=10` | News related to that coin | Yes |\n| 1c | `news_feed_get_social_sentiment` | `coin={coin}` | Social sentiment for that coin | Yes |\n\n### Step 3: LLM Aggregation\n\nThe LLM must:\n1. De-duplicate events and news (the same event may appear in both feeds)\n2. Rank by impact\u002Fimportance\n3. Categorize (Regulation, Projects, Market, Technology, etc.)\n4. Combine with social sentiment to identify market focus areas\n\n### Step 4: Output Structured Briefing\n\n---\n\n## Report Template\n\n```markdown\n## Crypto Industry News Briefing\n\n> Time range: Past {time_range} | Generated: {timestamp}\n\n### ? Major Events\n\n{Top 1-3 events by impact, each containing:}\n\n**1. {event_title}**\n- Time: {event_time}\n- Impact: {Market\u002Findustry impact assessment}\n- Involved: {Related coins\u002Fprojects\u002Finstitutions}\n- Details: {2-3 sentence summary}\n\n**2. {event_title}**\n- ...\n\n---\n\n### ? Trending News\n\n{Grouped by category, 2-5 items per category:}\n\n**Regulation & Policy**\n1. {title} — {source} ({time})\n   {One-sentence summary}\n2. ...\n\n**Projects & Technology**\n1. {title} — {source} ({time})\n   {One-sentence summary}\n2. ...\n\n**Market & Trading**\n1. {title} — {source} ({time})\n   {One-sentence summary}\n2. ...\n\n**DeFi \u002F NFT \u002F GameFi** (if applicable)\n1. ...\n\n---\n\n### ? Social Sentiment\n\n| Metric | Status |\n|--------|--------|\n| Overall Sentiment | {Bullish\u002FBearish\u002FNeutral} |\n| Discussion Volume | {High\u002FMedium\u002FLow} |\n| Trending Topics | {topic1}, {topic2}, {topic3} |\n| KOL Focus | {focus description} |\n\n**Top 5 Coins by Discussion Volume** (if data available)\n\n| Rank | Coin | Volume Change | Sentiment |\n|------|------|--------------|-----------|\n| 1 | {coin} | +{change}% | {Bullish\u002FBearish} |\n| 2 | ... | ... | ... |\n\n---\n\n### ? Worth Watching\n\n{LLM distills 2-3 noteworthy points from news and sentiment:}\n- {Point 1}\n- {Point 2}\n- {Point 3}\n\n> The above is a news summary and does not constitute investment advice.\n```\n\n### Coin-Specific Mode Template\n\n```markdown\n## {symbol} News Briefing\n\n> Time range: Past {time_range} | Generated: {timestamp}\n\n### Recent Key Events\n\n1. {event} — {time}\n   {details}\n2. ...\n\n### Related News\n\n1. [{title}]({url}) — {source} ({time})\n   {summary}\n2. ...\n\n### Social Sentiment\n\n- Discussion Volume: {High\u002FMedium\u002FLow} (vs 7-day average: {change}%)\n- Sentiment Bias: {Bullish\u002FBearish\u002FNeutral}\n- KOL Views: {Summary of key KOL opinions}\n\n### Summary\n\n{1-2 sentence summary of the coin's recent news landscape}\n```\n\n---\n\n## De-duplication & Ranking Logic\n\n| Rule | Description |\n|------|-------------|\n| Event-News de-duplication | If an event title closely matches a news headline (similarity > 80%), merge into one entry — events take priority |\n| Importance ranking | Events ranked by impact rating; news ranked by `importance` field |\n| Time ordering | At equal importance, reverse chronological (newest first) |\n| Categorization | News auto-categorized: Regulation & Policy \u002F Projects & Technology \u002F Market & Trading \u002F DeFi \u002F Other |\n\n---\n\n## Error Handling\n\n| Error Type | Handling |\n|------------|----------|\n| `news_events_get_latest_events` fails | Skip \"Major Events\" section; show news only |\n| `news_feed_search_news` fails | Show events only; note \"News feed temporarily unavailable\" |\n| `news_feed_get_social_sentiment` fails | Skip \"Social Sentiment\" section |\n| All Tools fail | Return error message; suggest the user try again later |\n| Too few news items (\u003C 3) | Expand time range (e.g., 24h → 48h) and note the change |\n\n---\n\n## Cross-Skill Routing\n\n| User Follow-up Intent | Route To |\n|-----------------------|----------|\n| \"Why did XX pump\u002Fdump?\" | `gate-news-eventexplain` |\n| \"Analyze XX for me\" | `gate-info-coinanalysis` |\n| \"How's the overall market?\" | `gate-info-marketoverview` |\n| \"Any new listings on Binance?\" | `gate-news-listing` |\n| \"Tell me more about ETF\" | Deep search via `news_feed_search_news(query=\"ETF\")` |\n\n---\n\n## Safety Rules\n\n1. **Source attribution**: Every news item must include the source (media name) and time\n2. **No interpretive speculation**: News summaries must remain objective — no subjective extrapolation\n3. **No fabricated news**: If data is insufficient, reduce the number of items rather than fabricate content\n4. **Neutral handling of sensitive topics**: Maintain neutral tone when covering regulation, politics, or other sensitive subjects\n5. **Timeliness labeling**: Clearly label the time range covered by the data\n",{"name":5,"updated":49,"version":50,"description":7,"required_env_vars":51,"required_credentials":52,"required_permissions":53},"2026-04-07","2026.4.7-1",[],[],[],"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fexchanges\u002Fgate-news-briefing",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-14 02:27:51",{"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-news-briefing",{"tool":69,"command":70},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill gate-news-briefing",{"tool":72,"command":73},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill gate-news-briefing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002FSKILL.md",true,[77,83,87,91,95,99,103,107,111,115],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"_meta.json","REFERENCE","参考文档",137,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002F_meta.json",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"CHANGELOG.md",726,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002FCHANGELOG.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"README.md",1855,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002FREADME.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fgate-runtime-rules.md",1225,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002Freferences\u002Fgate-runtime-rules.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Finfo-news-runtime-rules.md",1142,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002Freferences\u002Finfo-news-runtime-rules.md",{"path":100,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fmcp.md",3276,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002Freferences\u002Fmcp.md",{"path":104,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fscenarios.md",1989,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002Freferences\u002Fscenarios.md",{"path":108,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":109,"sourceHtmlUrl":110},"skill-card.md",2387,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002Fskill-card.md",{"path":112,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":113,"sourceHtmlUrl":114},"SOURCE.md",338,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002FSOURCE.md",{"path":116,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":117,"sourceHtmlUrl":118},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fgate-news-briefing\u002FTRUST.auto.yaml",[120,148,171,189,202,212],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":44},"01M712C436EQYE43342Q4E7GG1","recipe-performance","Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FSKILL.md",[],[129,130,131,132,133,134,135,136,137,138,139,140,42,141,142,143,144,145,146,147],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","tasks","react","browser","layout","screen","network","metamask",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":44},"01M70XT2F8A5CQZ81JBP98KSW3","mexc-spot-websocket","MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FSKILL.md",[],[157,158,159,160,161,162,163,164,165,166,167,168,169,170],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":175,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":44},"01M70XT0MBXN3WZY1BKN0CPNKR","mexc-spot-rest","MEXC Spot REST workflows for public data, signed account requests, orders, wallet\u002Fadmin actions, and secure signing without exposing API keys.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FSKILL.md",[],[179,158,180,181,182,183,184,168,167,166,185,186,187,162,188,161,160],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":152,"licenseFileUrl":193,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":44},"01M70XSYSVZ2N0N91XCAR2CAK0","mexc-futures-websocket","MEXC Futures WebSocket workflows for public streams, private account\u002Forder\u002Fposition streams, ping\u002Fpong, subscriptions, and depth maintenance.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FSKILL.md",[],[197,198,159,199,200,169,167,201,165,164,162,161],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":203,"name":204,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":44},"01M6H0ZWHVE5W04WG2DKQE2SQC","0xklen-version-and-refresh-sanctions-lists","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FSKILL.md",[],[209,210,211],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":216,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":44},"01M6H0Z28Q3R8J0S799GJQWXM3","verify-tests-cover-changed-lines","Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FSKILL.md",[],[220,221,222,223,224,225,226,40,227,228,229],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]