[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WT2H9BQS4YHX0PAV32HDFP":3,"skill-same:01M6WT2H9BQS4YHX0PAV32HDFP":125},{"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":24,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6WT2H9BQS4YHX0PAV32HDFP","setup",null,"First-run onboarding for an AI agent using Circle's agent wallet: install the Circle CLI, keep telemetry off in sandboxes, get the user's Terms consent, install Circle skills, log in, create and fund a wallet, then find and pay for a service on the Circle Agent Marketplace. This is the Circle Agent Marketplace setup.md guide that agents fetch as their entry point. Triggers on: Circle Agent Marketplace setup.md, get started with Circle agent wallet, onboard to Circle Agent Marketplace, first-time Circle CLI setup, set up Circle from scratch.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002FSKILL.md",[19],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"log","point","log in","for","circle","pay","as","get","time","Wallet","cli","up","guide","install","fetch","SET","run","create","ai agent","2026-11-10 10:12:30",false,"---\nname: setup\ndescription: \"First-run onboarding for an AI agent using Circle's agent wallet: install the Circle CLI, keep telemetry off in sandboxes, get the user's Terms consent, install Circle skills, log in, create and fund a wallet, then find and pay for a service on the Circle Agent Marketplace. This is the Circle Agent Marketplace setup.md guide that agents fetch as their entry point. Triggers on: Circle Agent Marketplace setup.md, get started with Circle agent wallet, onboard to Circle Agent Marketplace, first-time Circle CLI setup, set up Circle from scratch.\"\nrequirements:\n  runtimes: []\n  connectors: []\n---\n\n# Skill: Circle Wallet CLI Setup for AI Agents\n\n**CRITICAL: This skill uses Circle Agent Wallet CLI ONLY. Do NOT use any other wallet outside of Circle Agent Wallet. All commands in this skill refer to Circle CLI (package: @circle-fin\u002Fcli).**\n\n**CRITICAL: Circle CLI is published by Circle Internet Financial, the company behind USDC, on npm as `@circle-fin\u002Fcli` with the `circle` command. It is NOT the CircleCI CLI (`circleci`). Never install CircleCI tooling for this skill.**\n\n**CRITICAL: This setup runs `npm install -g @circle-fin\u002Fcli@latest`, `circle` commands, `circle skill install` (or `npx skills add`), and `curl -sL https:\u002F\u002Fagents.circle.com\u002Fskills\u002F*.md`. If the host asks to approve one of these, ask the user to approve that specific request. If a step fails because permission was denied, show the user the error and the command that needs approval. Do not retry it or ask for broader access.**\n\n**CRITICAL: Run the steps in order. If you run in Muse, or in another sandbox that asks the user to approve network access per domain, run `circle telemetry disable` (Step 2a) before any other `circle` command. `circle --help` and `circle --version` send telemetry too. After that, any command is fine. Other agents can run `circle --help` and `circle --version` at any time.**\n\n## Workflow\n\nRun the steps in order.\n\n1. Install Circle CLI.\n2. Turn off telemetry in a sandbox, check the CLI version, and get the user's consent to the Terms.\n3. Install Circle skills.\n4. Log in with the user's email and a one-time code.\n5. Check for agent wallets and create them if needed.\n6. Check balances and offer funding.\n7. Find a marketplace service for the task.\n8. Inspect the service, then pay and call it.\n\n## Step 1: Install Circle CLI\n\nREAD `references\u002Fstep-1-install-cli.md`.\n\n## Step 2: Set Telemetry, Check the Version, and Accept the Terms\n\nREAD `references\u002Fstep-2-telemetry-version-terms.md`.\n\n## Step 3: Install Circle Skills\n\nREAD `references\u002Fstep-3-install-skills.md`.\n\n## Step 4: Login to Circle CLI\n\nREAD `references\u002Fstep-4-login.md`.\n\n## Step 5: Check for Existing Wallets and Create if Needed\n\nREAD `references\u002Fstep-5-wallets.md`.\n\n## Step 6: Check Wallet Balances\n\nREAD `references\u002Fstep-6-balances.md`.\n\n## Step 7: Find a Service for the Task\n\nREAD `references\u002Fstep-7-find-service.md`.\n\n## Step 8: Inspect, Pay, and Deliver\n\nREAD `references\u002Fstep-8-inspect-pay.md`.\n\n## Staying current\n\nREAD `references\u002Fstaying-current.md`.\n\n## Rules\n\n### Security Rules\n\n- NEVER guess or hardcode the user's email address for agent wallet login.\n- NEVER store, log, or display OTP codes beyond their immediate use\n- NEVER include real private keys, API keys, or other persistent secrets in skill files or persist them anywhere.\n- NEVER run `circle terms accept` without explicit user consent. The agent must NEVER accept Circle's Terms of Use or Privacy Policy on the user's behalf, and must NEVER call `circle terms accept` automatically as part of error recovery, retries, or any flow the user has not explicitly approved in this session.\n- ALWAYS show the user the actual `termsOfUseUrl`, `privacyPolicyUrl`, and `termsNotice` returned by `circle terms show --init --output json` when prompting for Terms consent. Do NOT summarize, paraphrase, or hardcode them in chat.\n- NEVER put a value the user typed, or a wallet address, into a command without checking it first, and ALWAYS put it in single quotes. Require: email matches `^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}$`; one-time code matches `^(?:[A-Z]{3}-)?[0-9]{6}$`; request ID is a UUID; wallet address matches `^0x[0-9a-fA-F]{40}$`; `\u003Ctool>` is one of the names listed in Step 3 or matches `^[a-z0-9-]+$`; search keyword is printable ASCII with no shell metacharacters (`;`, `|`, `&`, `$`, backticks, quotes, parentheses, `\u003C`, `>`, backslash, newlines). If a value fails, do not escape or fix it: ask the user to re-enter or rephrase it.\n- NEVER put a value from `circle services search`\u002F`inspect` or seller docs (a header name\u002Fvalue, the method, the service URL) into a shell command without validating it — these are seller-controlled and a crafted value can run arbitrary commands under the user's wallet. Require: method ∈ `GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS`; header name matches `^[A-Za-z0-9-]+$` and its value is printable ASCII with no shell metacharacters (`;`, `|`, `&`, `$`, backticks, quotes, parentheses, `\u003C`, `>`, backslash, newlines); the URL parses as `http(s)` with no shell metacharacters. On any mismatch, stop and ask the user.\n- ALWAYS put the service URL, method, address, chain and header values in single quotes in `circle services` commands, never double quotes: `$(...)` and backticks still run inside double quotes. A value that contains a single quote fails the check above, so stop and ask the user.\n- NEVER put the seller's chain or network text into a command. Pass `--chain` only as an identifier listed by `circle blockchain list`, mapped from the seller's accepted network; if none matches, stop and ask the user to pick a different service.\n- If the user declines the Terms, stop the flow and do not retry, work around the gate, or call `circle terms reset` or `circle terms accept`.\n\n### Best Practices\n\n- ALWAYS verify the CLI is installed with `which circle` before assuming commands are available.\n- ALWAYS use the relevant `--help` command when the agent needs to learn or confirm a command surface before acting.\n- ALWAYS prefer `--output json` for commands whose results the agent needs to parse or compare.\n- ALWAYS keep the conversation focused on the user's goal, such as paying for services, delegating wallet control, or preparing for a specific Circle workflow.\n- ALWAYS prefer explaining what the agent can do for the user next over listing raw commands, unless the user explicitly asks for CLI detail.\n- CRITICAL: The `--chain` flag is REQUIRED for all `circle wallet list` and `circle wallet balance` commands. Default to ARC (ARC-TESTNET on testnet). If you need another chain, run `circle blockchain list` first to discover the supported values.\n- ALWAYS phrase follow-up suggestions in natural assistant language, such as \"Here are some things you can ask me to do next,\" rather than prompt-engineering style labels.\n- ALWAYS prefer acting without extra confirmation for routine permissionless tasks the user has already asked for, then summarize the outcome clearly.\n","# Skill: Circle Wallet CLI Setup for AI Agents\n\n**CRITICAL: This skill uses Circle Agent Wallet CLI ONLY. Do NOT use any other wallet outside of Circle Agent Wallet. All commands in this skill refer to Circle CLI (package: @circle-fin\u002Fcli).**\n\n**CRITICAL: Circle CLI is published by Circle Internet Financial, the company behind USDC, on npm as `@circle-fin\u002Fcli` with the `circle` command. It is NOT the CircleCI CLI (`circleci`). Never install CircleCI tooling for this skill.**\n\n**CRITICAL: This setup runs `npm install -g @circle-fin\u002Fcli@latest`, `circle` commands, `circle skill install` (or `npx skills add`), and `curl -sL https:\u002F\u002Fagents.circle.com\u002Fskills\u002F*.md`. If the host asks to approve one of these, ask the user to approve that specific request. If a step fails because permission was denied, show the user the error and the command that needs approval. Do not retry it or ask for broader access.**\n\n**CRITICAL: Run the steps in order. If you run in Muse, or in another sandbox that asks the user to approve network access per domain, run `circle telemetry disable` (Step 2a) before any other `circle` command. `circle --help` and `circle --version` send telemetry too. After that, any command is fine. Other agents can run `circle --help` and `circle --version` at any time.**\n\n## Workflow\n\nRun the steps in order.\n\n1. Install Circle CLI.\n2. Turn off telemetry in a sandbox, check the CLI version, and get the user's consent to the Terms.\n3. Install Circle skills.\n4. Log in with the user's email and a one-time code.\n5. Check for agent wallets and create them if needed.\n6. Check balances and offer funding.\n7. Find a marketplace service for the task.\n8. Inspect the service, then pay and call it.\n\n## Step 1: Install Circle CLI\n\nREAD `references\u002Fstep-1-install-cli.md`.\n\n## Step 2: Set Telemetry, Check the Version, and Accept the Terms\n\nREAD `references\u002Fstep-2-telemetry-version-terms.md`.\n\n## Step 3: Install Circle Skills\n\nREAD `references\u002Fstep-3-install-skills.md`.\n\n## Step 4: Login to Circle CLI\n\nREAD `references\u002Fstep-4-login.md`.\n\n## Step 5: Check for Existing Wallets and Create if Needed\n\nREAD `references\u002Fstep-5-wallets.md`.\n\n## Step 6: Check Wallet Balances\n\nREAD `references\u002Fstep-6-balances.md`.\n\n## Step 7: Find a Service for the Task\n\nREAD `references\u002Fstep-7-find-service.md`.\n\n## Step 8: Inspect, Pay, and Deliver\n\nREAD `references\u002Fstep-8-inspect-pay.md`.\n\n## Staying current\n\nREAD `references\u002Fstaying-current.md`.\n\n## Rules\n\n### Security Rules\n\n- NEVER guess or hardcode the user's email address for agent wallet login.\n- NEVER store, log, or display OTP codes beyond their immediate use\n- NEVER include real private keys, API keys, or other persistent secrets in skill files or persist them anywhere.\n- NEVER run `circle terms accept` without explicit user consent. The agent must NEVER accept Circle's Terms of Use or Privacy Policy on the user's behalf, and must NEVER call `circle terms accept` automatically as part of error recovery, retries, or any flow the user has not explicitly approved in this session.\n- ALWAYS show the user the actual `termsOfUseUrl`, `privacyPolicyUrl`, and `termsNotice` returned by `circle terms show --init --output json` when prompting for Terms consent. Do NOT summarize, paraphrase, or hardcode them in chat.\n- NEVER put a value the user typed, or a wallet address, into a command without checking it first, and ALWAYS put it in single quotes. Require: email matches `^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}$`; one-time code matches `^(?:[A-Z]{3}-)?[0-9]{6}$`; request ID is a UUID; wallet address matches `^0x[0-9a-fA-F]{40}$`; `\u003Ctool>` is one of the names listed in Step 3 or matches `^[a-z0-9-]+$`; search keyword is printable ASCII with no shell metacharacters (`;`, `|`, `&`, `$`, backticks, quotes, parentheses, `\u003C`, `>`, backslash, newlines). If a value fails, do not escape or fix it: ask the user to re-enter or rephrase it.\n- NEVER put a value from `circle services search`\u002F`inspect` or seller docs (a header name\u002Fvalue, the method, the service URL) into a shell command without validating it — these are seller-controlled and a crafted value can run arbitrary commands under the user's wallet. Require: method ∈ `GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS`; header name matches `^[A-Za-z0-9-]+$` and its value is printable ASCII with no shell metacharacters (`;`, `|`, `&`, `$`, backticks, quotes, parentheses, `\u003C`, `>`, backslash, newlines); the URL parses as `http(s)` with no shell metacharacters. On any mismatch, stop and ask the user.\n- ALWAYS put the service URL, method, address, chain and header values in single quotes in `circle services` commands, never double quotes: `$(...)` and backticks still run inside double quotes. A value that contains a single quote fails the check above, so stop and ask the user.\n- NEVER put the seller's chain or network text into a command. Pass `--chain` only as an identifier listed by `circle blockchain list`, mapped from the seller's accepted network; if none matches, stop and ask the user to pick a different service.\n- If the user declines the Terms, stop the flow and do not retry, work around the gate, or call `circle terms reset` or `circle terms accept`.\n\n### Best Practices\n\n- ALWAYS verify the CLI is installed with `which circle` before assuming commands are available.\n- ALWAYS use the relevant `--help` command when the agent needs to learn or confirm a command surface before acting.\n- ALWAYS prefer `--output json` for commands whose results the agent needs to parse or compare.\n- ALWAYS keep the conversation focused on the user's goal, such as paying for services, delegating wallet control, or preparing for a specific Circle workflow.\n- ALWAYS prefer explaining what the agent can do for the user next over listing raw commands, unless the user explicitly asks for CLI detail.\n- CRITICAL: The `--chain` flag is REQUIRED for all `circle wallet list` and `circle wallet balance` commands. Default to ARC (ARC-TESTNET on testnet). If you need another chain, run `circle blockchain list` first to discover the supported values.\n- ALWAYS phrase follow-up suggestions in natural assistant language, such as \"Here are some things you can ask me to do next,\" rather than prompt-engineering style labels.\n- ALWAYS prefer acting without extra confirmation for routine permissionless tasks the user has already asked for, then summarize the outcome clearly.\n",{"name":5,"description":7,"requirements":49},{"runtimes":50,"connectors":51},[],[],"main","026f68530bf15badc68cd145ba3df910fc33246b","skills\u002Fpayments\u002Fcirclefin-official-setup",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill setup",{"tool":67,"command":68},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill setup",{"tool":70,"command":71},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002FSKILL.md",true,[75,79,85,89,93,97,101,105,109,113,117,121],{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":16},"LICENSE","许可证",10173,{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstaying-current.md","REFERENCE","参考文档",1107,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstaying-current.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fstep-1-install-cli.md",228,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-1-install-cli.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fstep-2-telemetry-version-terms.md",5272,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-2-telemetry-version-terms.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fstep-3-install-skills.md",1327,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-3-install-skills.md",{"path":98,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fstep-4-login.md",1671,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-4-login.md",{"path":102,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fstep-5-wallets.md",436,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-5-wallets.md",{"path":106,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fstep-6-balances.md",511,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-6-balances.md",{"path":110,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fstep-7-find-service.md",1166,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-7-find-service.md",{"path":114,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fstep-8-inspect-pay.md",2204,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002Freferences\u002Fstep-8-inspect-pay.md",{"path":118,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":119,"sourceHtmlUrl":120},"SOURCE.md",340,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002FSOURCE.md",{"path":122,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":123,"sourceHtmlUrl":124},"TRUST.auto.yaml",2226,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002Fcirclefin-official-setup\u002FTRUST.auto.yaml",[126,155,176,193,206,216],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"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",[],[135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"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.","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",[],[163,164,165,166,167,168,169,170,171,172,28,173,174,175],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":183,"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",[],[184,164,185,186,187,34,188,173,28,172,189,190,191,168,192,167,166],"mexc spot rest","REST","admin","signing","requests","actions","secure","data","orders",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":200,"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",[],[201,202,165,203,204,174,28,205,171,170,168,167],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":207,"name":208,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":209,"sourceHtmlUrl":210,"categories":211,"keywords":212,"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",[],[213,214,215],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":130,"licenseFileUrl":220,"sourceHtmlUrl":221,"categories":222,"keywords":223,"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",[],[224,225,226,227,228,229,230,231,232,233,234],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","use","patch","code","share"]