[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GS441FS5C4W7S57SSMATNN":3,"skill-same:01M6GS441FS5C4W7S57SSMATNN":113},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":29,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6GS441FS5C4W7S57SSMATNN","ctf-similar-search",null,"Searches for similar CTF challenge writeups using Tavily API for search and content extraction. Use when the user requests finding related challenges, when solve-challenge has failed multiple times and needs reference solutions, or when first identifying a challenge type and seeking examples.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",80,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"search","ctf similar search","ctf","use","solutions","when","for","true","requests","with","name","type","writeups","solve","tavily","write","read","challenge","filesystem","Bash","api","first","examples","code","packages","python","2026-11-10 10:12:30",false,"---\nname: ctf-similar-search\ndescription: Searches for similar CTF challenge writeups using Tavily API for search and content extraction. Use when the user requests finding related challenges, when solve-challenge has failed multiple times and needs reference solutions, or when first identifying a challenge type and seeking examples.\nlicense: MIT\ncompatibility: Requires filesystem-based agent (Claude Code or similar) with bash and Python 3 with requests and tavily packages.\nallowed-tools: Bash Read Write Glob Grep Skill\nmetadata:\n  user-invocable: \"true\"\n  argument-hint: \"\u003Cchallenge-name-or-clues>\"\n  author: Lukasz Jagiello\n---\n\n# CTF Similar Challenge Search\n\nSearch for similar CTF challenge writeups using Tavily API.\n\n## Prerequisites\n\n```bash\npip install requests tavily\n```\n\nSet your Tavily API key (from https:\u002F\u002Ftavily.com) before running:\n\n```bash\nexport TAVILY_API_KEY='tvly-...'\n```\n\n## API Overview\n\nThis skill provides two interfaces:\n\n| Interface | Purpose | Command |\n|-----------|---------|---------|\n| **Tavily Search** | Search for writeups and articles | `.\u002Fsearch.sh search \u003Ckeyword>` |\n| **Tavily Extract** | Extract content from URLs | `.\u002Fsearch.sh extract \u003Curl1> [url2] ...` |\n\n## Search Workflow\n\n### Step 1: Search with Keywords\n\nChoose keywords based on available information:\n\n#### Scenario 1: Known Competition + Challenge Name\n```bash\n# Format: [Competition Name] [Challenge Name] — max 3 words\n.\u002Fsearch.sh search \"DASCTF URL Storage\"\n.\u002Fsearch.sh search \"HGAME baby web\"\n.\u002Fsearch.sh search \"BUUCTF pwn1\"\n```\n\n#### Scenario 2: Challenge Name Only (no competition info)\n```bash\n# Use challenge name directly — max 3 words\n.\u002Fsearch.sh search \"URL Storage\"\n.\u002Fsearch.sh search \"baby overflow\"\n.\u002Fsearch.sh search \"crypto-rsa\"\n```\n\n#### Scenario 3: Unique Identifiers (code snippets, strings)\n```bash\n# Use unique, non-trivial strings from the challenge — NO word limit\n.\u002Fsearch.sh search \"def encrypt_flag(key): return base64\"\n.\u002Fsearch.sh search \"CUSTOM_MAGIC_BYTES\"\n.\u002Fsearch.sh search \"ERROR: invalid padding in AES block\"\n```\n\n### ⚠️ Critical: 3-Word Limit for Non-Code Queries\n\n**All keyword searches that are NOT code snippets or unique identifier strings MUST NOT exceed 3 words.** This constraint ensures precise, focused queries that return relevant CTF writeup results instead of broad, diluted searches.\n\n| Search Type | Word Limit | Examples |\n|-------------|-----------|----------|\n| Competition + Challenge name | ≤ 3 words | `\"DASCTF URL Storage\"`, `\"HGAME baby web\"` |\n| Challenge name only | ≤ 3 words | `\"URL Storage\"`, `\"baby overflow\"` |\n| Code snippets \u002F strings | **No limit** | `\"def encrypt_flag(key): return base64\"` |\n| Error messages \u002F identifiers | **No limit** | `\"CUSTOM_MAGIC_BYTES\"`, `\"ERROR: invalid padding in AES block\"` |\n\n**For competition + challenge name searches**, drop filler words (year numbers, \"CTF\", \"competition\", \"writeup\", \"solution\") and keep only the 3 most distinctive words:\n\n- ❌ `\"HGAME 2024 baby web challenge\"` (5 words)\n- ✅ `\"HGAME baby web\"` (3 words)\n- ❌ `\"DASCTF 2023 URL Storage writeup\"` (5 words)\n- ✅ `\"DASCTF URL Storage\"` (3 words)\n- ❌ `\"PlaidCTF 2025 zero day exploit solution\"` (6 words)\n- ✅ `\"PlaidCTF zero day\"` (3 words)\n\n**For code\u002Fstring searches**, use the entire unique snippet — these are exempt from the word limit:\n\n- ✅ `\"def xor_encrypt(data, key):\"` (code — exempt)\n- ✅ `\"ERROR: invalid padding in AES block\"` (error string — exempt)\n- ✅ `\"CUSTOM_MAGIC_BYTES\"` (identifier — exempt)\n\n### Keyword Rules\n\n| ✅ Good Keywords | ❌ Bad Keywords |\n|------------------|-----------------|\n| Competition + Challenge name (≤3 words) | Single vulnerability type (SSRF, XSS) |\n| Challenge name (≤3 words) | Generic terms (web, pwn, crypto) |\n| Unique code snippets (no word limit) | Full sentences |\n| Specific error messages (no word limit) | Articles (a, the, in) |\n| Library\u002Fframework names | Generic strings (flag{}, etc.) |\n| Custom function names | Tool names alone |\n\n**Why avoid these?**\n- \"SSRF\" → returns generic vulnerability explanations, not CTF writeups\n- \"flag{\" → returns millions of unrelated results\n- \"URL Storage DASCTF\" → returns specific CTF challenges\n\n**Why the 3-word limit?**\n- Forces precision: only the most distinctive keywords survive\n- Filters noise: filler words like \"challenge\", \"writeup\", \"solution\" dilute results\n- Improves API efficiency: shorter, focused queries consume fewer credits\n\n**Key principle:** Use keywords that uniquely identify THIS challenge, not the general technique or common patterns. Keep non-code queries to 3 words or fewer.\n\n### Step 2: Review Search Results\n\nThe search returns:\n- **Answer**: AI-generated summary if available\n- **Results**: List of URLs with titles and content previews\n- **Credits**: API usage information\n\n### Step 3: Extract Content (Optional)\n\nIf a search result looks promising, extract its full content:\n\n```bash\n# Single URL\n.\u002Fsearch.sh extract \"https:\u002F\u002Fexample.com\u002Fwriteup\"\n\n# Multiple URLs\n.\u002Fsearch.sh extract \"https:\u002F\u002Furl1.com\" \"https:\u002F\u002Furl2.com\"\n```\n\n### Step 4: Analyze and Pivot\n\nBased on extracted content:\n- Identify common techniques used in similar challenges\n- Determine if the approach is applicable\n- Pivot to category-specific skill if needed\n\n## When to Pivot\n\n- If the challenge is already well-categorized, use the specific `ctf-*` skill\n- If you need OSINT techniques, use `ctf-osint`\n- If you need to generate a writeup after solving, use `ctf-writeup`\n\n## Quick Start\n\n```bash\n# Scenario 1: Competition + Challenge name (≤3 words)\n.\u002Fsearch.sh search \"DASCTF URL Storage\"\n\n# Scenario 2: Challenge name only (≤3 words)\n.\u002Fsearch.sh search \"URL Storage\"\n\n# Scenario 3: Unique identifier from challenge (no word limit)\n.\u002Fsearch.sh search \"def xor_encrypt(data, key):\"\n.\u002Fsearch.sh search \"ERROR: invalid padding\"\n\n# Extract content from promising results\n.\u002Fsearch.sh extract \"https:\u002F\u002Fctftime.org\u002Fwriteup\u002F12345\"\n```\n\n## Tips\n\n1. **Be specific**: Use competition name + challenge name when available\n2. **Use unique strings**: Code snippets, error messages, unique identifiers\n3. **Avoid generic terms**: Don't search \"SSRF CTF writeup\" - too broad\n4. **Review first**: Check search results before extracting\n5. **Extract selectively**: Only extract URLs that look relevant\n6. **Respect the 3-word limit**: For non-code queries, strip filler words and keep only the 3 most distinctive keywords\n\n$ARGUMENTS\n","# CTF Similar Challenge Search\n\nSearch for similar CTF challenge writeups using Tavily API.\n\n## Prerequisites\n\n```bash\npip install requests tavily\n```\n\nSet your Tavily API key (from https:\u002F\u002Ftavily.com) before running:\n\n```bash\nexport TAVILY_API_KEY='tvly-...'\n```\n\n## API Overview\n\nThis skill provides two interfaces:\n\n| Interface | Purpose | Command |\n|-----------|---------|---------|\n| **Tavily Search** | Search for writeups and articles | `.\u002Fsearch.sh search \u003Ckeyword>` |\n| **Tavily Extract** | Extract content from URLs | `.\u002Fsearch.sh extract \u003Curl1> [url2] ...` |\n\n## Search Workflow\n\n### Step 1: Search with Keywords\n\nChoose keywords based on available information:\n\n#### Scenario 1: Known Competition + Challenge Name\n```bash\n# Format: [Competition Name] [Challenge Name] — max 3 words\n.\u002Fsearch.sh search \"DASCTF URL Storage\"\n.\u002Fsearch.sh search \"HGAME baby web\"\n.\u002Fsearch.sh search \"BUUCTF pwn1\"\n```\n\n#### Scenario 2: Challenge Name Only (no competition info)\n```bash\n# Use challenge name directly — max 3 words\n.\u002Fsearch.sh search \"URL Storage\"\n.\u002Fsearch.sh search \"baby overflow\"\n.\u002Fsearch.sh search \"crypto-rsa\"\n```\n\n#### Scenario 3: Unique Identifiers (code snippets, strings)\n```bash\n# Use unique, non-trivial strings from the challenge — NO word limit\n.\u002Fsearch.sh search \"def encrypt_flag(key): return base64\"\n.\u002Fsearch.sh search \"CUSTOM_MAGIC_BYTES\"\n.\u002Fsearch.sh search \"ERROR: invalid padding in AES block\"\n```\n\n### ⚠️ Critical: 3-Word Limit for Non-Code Queries\n\n**All keyword searches that are NOT code snippets or unique identifier strings MUST NOT exceed 3 words.** This constraint ensures precise, focused queries that return relevant CTF writeup results instead of broad, diluted searches.\n\n| Search Type | Word Limit | Examples |\n|-------------|-----------|----------|\n| Competition + Challenge name | ≤ 3 words | `\"DASCTF URL Storage\"`, `\"HGAME baby web\"` |\n| Challenge name only | ≤ 3 words | `\"URL Storage\"`, `\"baby overflow\"` |\n| Code snippets \u002F strings | **No limit** | `\"def encrypt_flag(key): return base64\"` |\n| Error messages \u002F identifiers | **No limit** | `\"CUSTOM_MAGIC_BYTES\"`, `\"ERROR: invalid padding in AES block\"` |\n\n**For competition + challenge name searches**, drop filler words (year numbers, \"CTF\", \"competition\", \"writeup\", \"solution\") and keep only the 3 most distinctive words:\n\n- ❌ `\"HGAME 2024 baby web challenge\"` (5 words)\n- ✅ `\"HGAME baby web\"` (3 words)\n- ❌ `\"DASCTF 2023 URL Storage writeup\"` (5 words)\n- ✅ `\"DASCTF URL Storage\"` (3 words)\n- ❌ `\"PlaidCTF 2025 zero day exploit solution\"` (6 words)\n- ✅ `\"PlaidCTF zero day\"` (3 words)\n\n**For code\u002Fstring searches**, use the entire unique snippet — these are exempt from the word limit:\n\n- ✅ `\"def xor_encrypt(data, key):\"` (code — exempt)\n- ✅ `\"ERROR: invalid padding in AES block\"` (error string — exempt)\n- ✅ `\"CUSTOM_MAGIC_BYTES\"` (identifier — exempt)\n\n### Keyword Rules\n\n| ✅ Good Keywords | ❌ Bad Keywords |\n|------------------|-----------------|\n| Competition + Challenge name (≤3 words) | Single vulnerability type (SSRF, XSS) |\n| Challenge name (≤3 words) | Generic terms (web, pwn, crypto) |\n| Unique code snippets (no word limit) | Full sentences |\n| Specific error messages (no word limit) | Articles (a, the, in) |\n| Library\u002Fframework names | Generic strings (flag{}, etc.) |\n| Custom function names | Tool names alone |\n\n**Why avoid these?**\n- \"SSRF\" → returns generic vulnerability explanations, not CTF writeups\n- \"flag{\" → returns millions of unrelated results\n- \"URL Storage DASCTF\" → returns specific CTF challenges\n\n**Why the 3-word limit?**\n- Forces precision: only the most distinctive keywords survive\n- Filters noise: filler words like \"challenge\", \"writeup\", \"solution\" dilute results\n- Improves API efficiency: shorter, focused queries consume fewer credits\n\n**Key principle:** Use keywords that uniquely identify THIS challenge, not the general technique or common patterns. Keep non-code queries to 3 words or fewer.\n\n### Step 2: Review Search Results\n\nThe search returns:\n- **Answer**: AI-generated summary if available\n- **Results**: List of URLs with titles and content previews\n- **Credits**: API usage information\n\n### Step 3: Extract Content (Optional)\n\nIf a search result looks promising, extract its full content:\n\n```bash\n# Single URL\n.\u002Fsearch.sh extract \"https:\u002F\u002Fexample.com\u002Fwriteup\"\n\n# Multiple URLs\n.\u002Fsearch.sh extract \"https:\u002F\u002Furl1.com\" \"https:\u002F\u002Furl2.com\"\n```\n\n### Step 4: Analyze and Pivot\n\nBased on extracted content:\n- Identify common techniques used in similar challenges\n- Determine if the approach is applicable\n- Pivot to category-specific skill if needed\n\n## When to Pivot\n\n- If the challenge is already well-categorized, use the specific `ctf-*` skill\n- If you need OSINT techniques, use `ctf-osint`\n- If you need to generate a writeup after solving, use `ctf-writeup`\n\n## Quick Start\n\n```bash\n# Scenario 1: Competition + Challenge name (≤3 words)\n.\u002Fsearch.sh search \"DASCTF URL Storage\"\n\n# Scenario 2: Challenge name only (≤3 words)\n.\u002Fsearch.sh search \"URL Storage\"\n\n# Scenario 3: Unique identifier from challenge (no word limit)\n.\u002Fsearch.sh search \"def xor_encrypt(data, key):\"\n.\u002Fsearch.sh search \"ERROR: invalid padding\"\n\n# Extract content from promising results\n.\u002Fsearch.sh extract \"https:\u002F\u002Fctftime.org\u002Fwriteup\u002F12345\"\n```\n\n## Tips\n\n1. **Be specific**: Use competition name + challenge name when available\n2. **Use unique strings**: Code snippets, error messages, unique identifiers\n3. **Avoid generic terms**: Don't search \"SSRF CTF writeup\" - too broad\n4. **Review first**: Check search results before extracting\n5. **Extract selectively**: Only extract URLs that look relevant\n6. **Respect the 3-word limit**: For non-code queries, strip filler words and keep only the 3 most distinctive keywords\n\n$ARGUMENTS\n",{"name":5,"license":15,"metadata":61,"description":7,"allowed-tools":64,"compatibility":65},{"author":62,"argument-hint":63,"user-invocable":37},"Lukasz Jagiello","\u003Cchallenge-name-or-clues>","Bash Read Write Glob Grep Skill","Requires filesystem-based agent (Claude Code or similar) with bash and Python 3 with requests and tavily packages.","main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fdev-tools\u002Fljagiello-ctf-similar-search",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-11 08:47:40",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill ctf-similar-search",{"tool":81,"command":82},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill ctf-similar-search",{"tool":84,"command":85},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill ctf-similar-search","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002FSKILL.md",true,[89,93,99,103,109],{"path":90,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":16},"LICENSE","许可证",1072,{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"search.py","SCRIPT","脚本",6779,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002Fsearch.py",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"search.sh",565,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002Fsearch.sh",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"SOURCE.md","REFERENCE","参考文档",340,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002FSOURCE.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"TRUST.auto.yaml",2105,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Fljagiello-ctf-similar-search\u002FTRUST.auto.yaml",[114,142,163,180,193,203],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":56},"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.","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",[],[122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"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":146,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":56},"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",[],[151,152,153,50,154,155,156,157,158,159,36,160,161,162],"mexc spot websocket","spot","websocket","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":146,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":56},"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",[],[171,152,172,173,174,175,38,160,36,159,176,177,178,155,179,154,50],"mexc spot rest","REST","admin","signing","Wallet","actions","secure","data","orders",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":146,"licenseFileUrl":184,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":56},"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",[],[188,189,153,190,191,161,36,192,158,157,155,154],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":194,"name":195,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":56},"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",[],[200,201,202],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":207,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":56},"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",[],[211,212,213,214,215,216,217,33,218,53,219],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","share"]