[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSVF5QATHFV3H1W9Y020YY":3,"skill-same:01M6GSVF5QATHFV3H1W9Y020YY":91},{"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":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},"01M6GSVF5QATHFV3H1W9Y020YY","kraken-setup",null,"Install kraken-cli, create API credentials, and go from paper trading to live in under five minutes.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-kraken-setup\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-kraken-setup\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],"setup","kraken","kraken setup","cli","go","create","finance","credentials","api","install","trading","live","paper","minutes","2026-11-10 10:12:30",false,"---\nname: kraken-setup\nversion: 1.1.0\ndescription: \"Install kraken-cli, create API credentials, and go from paper trading to live in under five minutes.\"\nmetadata:\n  openclaw:\n    category: \"finance\"\n  requires:\n    bins: [\"kraken\"]\n---\n\n# kraken-setup\n\nFirst-run setup for `kraken-cli`. Covers install, credentials, paper trading, and handing off to an MCP client.\n\nUse this skill when a user says \"set up kraken-cli\", \"install kraken\", \"get started\", or similar. For wiring the running CLI into Claude, Cursor, Codex, or Gemini, hand off to `kraken-mcp-integration`.\n\n## 1. Install the CLI\n\nThe one-liner installs `kraken`, `kraken-mcp` (the MCP server) and\n`kraken-shell` (an interactive shell) into `~\u002F.cargo\u002Fbin`, or `$CARGO_HOME\u002Fbin` if `CARGO_HOME` is set:\n\n```bash\ncurl --proto '=https' --tlsv1.2 -LsSf https:\u002F\u002Fgithub.com\u002Fkrakenfx\u002Fkraken-cli\u002Freleases\u002Flatest\u002Fdownload\u002Fkraken-cli-installer.sh | sh\n```\n\nFrom source (Rust 1.97 or later), the same three binaries:\n\n```bash\ncargo install --locked --git https:\u002F\u002Fgithub.com\u002Fkrakenfx\u002Fkraken-cli kraken-cli\n```\n\nPrebuilt archives are on [GitHub Releases](https:\u002F\u002Fgithub.com\u002Fkrakenfx\u002Fkraken-cli\u002Freleases). Move\n`kraken`, `kraken-mcp` and `kraken-shell` into a directory on `$PATH`.\n\nThe installer adds `~\u002F.cargo\u002Fbin` (or `$CARGO_HOME\u002Fbin`) to PATH for new terminals only. If `kraken` is not found right after install, call it by its full path, `~\u002F.cargo\u002Fbin\u002Fkraken` or `$CARGO_HOME\u002Fbin\u002Fkraken`, and\ntell the user to restart the agent from a new terminal window.\n\nVerify:\n\n```bash\nkraken --version && kraken-mcp --version\n```\n\n## 2. Start with paper trading\n\nPaper trading uses live prices with a simulated balance. No API keys required. Start here.\n\n```bash\nkraken workspace create sandbox --capital 10000 --mode paper -o json\nexport KRAKEN_WORKSPACE=sandbox\nkraken paper buy BTCUSD 0.01 -o json\nkraken workspace status -o json\n```\n\nFutures paper trading has one account that no workspace scopes, and it refuses\nchanges while a workspace is selected, so clear it first:\n\n```bash\nunset KRAKEN_WORKSPACE\nkraken futures paper init --balance 10000 -o json\nkraken futures paper buy PF_XBTUSD 1 --leverage 10 --type market -o json\nkraken futures paper positions -o json\n```\n\nPublic market data also needs no credentials:\n\n```bash\nkraken ticker BTCUSD -o json\nkraken orderbook BTCUSD --count 10 -o json\n```\n\nMost agent workflows can do their entire first session on paper and public data.\n\n## 3. (Optional) Add API credentials for live trading\n\nOnly needed if you want to query your real account or place real orders.\n\n### Recommended key scope\n\nGenerate the narrowest key you can live with. An AI agent should never be able to move funds off the exchange.\n\n- **Never enable `Withdraw Funds`.** Without this permission, even a prompt-injection or credential-exfiltration attack cannot remove assets from your Kraken account.\n- **Start read-only.** `Query Funds`, `Query Open Orders & Trades`, and `Query Closed Orders & Trades` are safe for a first session.\n- **Add trading scopes only when you need them.** `Create & Modify Orders` and `Cancel\u002FClose Orders` unlock live trading; no other scope is required for spot.\n- **Enable IP allowlisting if the agent runs from a static IP.** Kraken's API settings page lets you lock a key to one or more source IPs.\n- **Rotate on host change.** If you switch machines or re-install the plugin, revoke the old key and generate a new one.\n\nManage keys at \u003Chttps:\u002F\u002Fwww.kraken.com\u002Fu\u002Fsecurity\u002Fapi>.\n\n### Provide the key and secret to your agent\n\nThe CLI resolves credentials from three tiers, in order: command-line flags (`--api-key` \u002F `--api-secret`), environment variables (`KRAKEN_API_KEY` \u002F `KRAKEN_API_SECRET`), then the active stored key in a secure local config file managed by the CLI (stored with user-only permissions under your OS's standard config directory). The stored key is either the key from `kraken auth set` or `kraken setup`, or the sign-in key from `kraken auth login`; `kraken auth switch` selects which one. When an active sign-in key expires, private commands fail with an `auth` error and a hint to sign in again or switch. The CLI does not fall back to the other key. Pick the path that matches your client.\n\n#### Claude Code plugin\n\nThe `kraken-cli` plugin starts `kraken-mcp -s market,paper,feedback` and asks for no API key: none of those tools needs one. `kraken-mcp` still reads the active stored key from the CLI's local config, so a key saved earlier with `kraken auth set` or `kraken auth login` on the same machine is available to it. To keep the plugin credential-less, run `kraken auth reset` before starting Claude.\n\n#### Cursor, Codex, Gemini CLI\n\nLike the Claude plugin, these hosts start `kraken-mcp` with no key of their own. Either export credentials in the shell that launches the agent:\n\n```bash\nexport KRAKEN_API_KEY=\"your-key\"\nexport KRAKEN_API_SECRET=\"your-secret\"\n```\n\n…or rely on the key you stored with `kraken auth set` or `kraken auth login` — the plugin reads the same config file as the standalone CLI, so one stored key serves both, and `kraken auth switch` changes it for both.\n\nFor futures, use a Kraken Futures key and set `KRAKEN_FUTURES_API_KEY` and `KRAKEN_FUTURES_API_SECRET` alongside the spot pair, or store both pairs once with `kraken auth set --api-key \u003Cspot-key> --api-secret-file \u003Cspot-secret-file> --futures-api-key \u003Cfutures-key> --futures-api-secret-stdin` and let the config file supply them. `auth set` always saves the spot pair too, so `--api-key` is required.\n\n#### Plain CLI use (not through a plugin)\n\n`kraken auth set` writes credentials to a secure local config file managed by the CLI (stored with user-only permissions in your OS's standard config directory). `kraken auth login` instead signs you in through the browser and stores the Spot API key it creates there: no withdrawal permissions, and an expiry date (90 days unless `--valid-for` says otherwise). It needs a terminal, so a person runs it, never an agent. `kraken auth show` displays the stored keys masked as `****wxyz` and the secret as `[REDACTED]`, and names the key in use, so you can confirm which key signs without exposing it. `kraken auth reset` clears the stored credentials; a sign-in key stays valid on Kraken until it expires.\n\n### Verify\n\n```bash\nkraken balance -o json\n```\n\nNever commit these values. `.env` and `.env.*` are already gitignored in the repo.\n\n## 4. Connect an MCP client\n\nThe CLI ships with a built-in MCP server. Point any MCP-compatible client (Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code, Windsurf) at it.\n\nSee `skills\u002Fkraken-mcp-integration\u002FSKILL.md` for the per-client config blocks and the full service reference.\n\nThe default MCP config in every `kraken-cli` marketplace listing (Claude, Cursor, Codex, Gemini) is `-s market,paper,feedback`:\n\n| Service | Auth | Why it's in the default |\n|---------|------|-------------------------|\n| `market` | None | Public price data, orderbooks, OHLC. |\n| `paper`  | None | Simulated trading with live prices. |\n| `feedback` | None | Lets the agent report friction or bugs. It uploads the text it writes, or a local file it names, to Kraken with no approval step; drop it from `-s` for an agent that reads untrusted input. |\n\nA fresh install can never place a real order. Live trading is an explicit\nopt-in: widen the service list in your MCP client's config to `-s market,trade,paper`\n(adds live spot orders) or `-s all` (everything, including funding and earn).\nSee the service table and the \"Enabling live trading\" section in\n`skills\u002Fkraken-mcp-integration\u002FSKILL.md` for the complete list and recommended\nprogression.\n\n## 5. Safety defaults\n\n- Commands flagged `dangerous` in `agents\u002Ftool-catalog.json` require explicit user confirmation. MCP surfaces this via the `destructive_hint` annotation.\n- Always try `--validate` before submitting a spot order. Futures orders have no dry run, so test them on `kraken futures paper` first.\n- Run paper-first, live-second. `skills\u002Fkraken-paper-to-live\u002FSKILL.md` covers the promotion checklist.\n\n## Troubleshooting\n\n**`kraken: command not found`**: the install directory isn't on `$PATH` yet. Open a new terminal, or call `~\u002F.cargo\u002Fbin\u002Fkraken` (or `$CARGO_HOME\u002Fbin\u002Fkraken`) by its full path.\n\n**`auth` error on every command**: you exported a key with insufficient permissions. Regenerate with the scopes above.\n\n**Futures commands fail with `auth` but spot works**: futures needs its own key. Set `KRAKEN_FUTURES_API_KEY` and `KRAKEN_FUTURES_API_SECRET`.\n\n**MCP client shows no Kraken tools**: confirm `kraken-mcp` is on the PATH the client sees (MCP clients often start with a minimal environment), or set `command` to the absolute path that `command -v kraken-mcp` prints in a new terminal. Most clients start the server without a shell, so `~` and `$CARGO_HOME` stay unexpanded. Releases before this one installed `kraken` only: run the one-liner again. Then see `kraken-mcp-integration` troubleshooting.\n\nIf you hit a mismatch between what you are trying to do and the CLI's interface or responses — including a mismatch between this skill and the installed CLI version's contract — feel free to submit feedback with `kraken feedback`.\n","# kraken-setup\n\nFirst-run setup for `kraken-cli`. Covers install, credentials, paper trading, and handing off to an MCP client.\n\nUse this skill when a user says \"set up kraken-cli\", \"install kraken\", \"get started\", or similar. For wiring the running CLI into Claude, Cursor, Codex, or Gemini, hand off to `kraken-mcp-integration`.\n\n## 1. Install the CLI\n\nThe one-liner installs `kraken`, `kraken-mcp` (the MCP server) and\n`kraken-shell` (an interactive shell) into `~\u002F.cargo\u002Fbin`, or `$CARGO_HOME\u002Fbin` if `CARGO_HOME` is set:\n\n```bash\ncurl --proto '=https' --tlsv1.2 -LsSf https:\u002F\u002Fgithub.com\u002Fkrakenfx\u002Fkraken-cli\u002Freleases\u002Flatest\u002Fdownload\u002Fkraken-cli-installer.sh | sh\n```\n\nFrom source (Rust 1.97 or later), the same three binaries:\n\n```bash\ncargo install --locked --git https:\u002F\u002Fgithub.com\u002Fkrakenfx\u002Fkraken-cli kraken-cli\n```\n\nPrebuilt archives are on [GitHub Releases](https:\u002F\u002Fgithub.com\u002Fkrakenfx\u002Fkraken-cli\u002Freleases). Move\n`kraken`, `kraken-mcp` and `kraken-shell` into a directory on `$PATH`.\n\nThe installer adds `~\u002F.cargo\u002Fbin` (or `$CARGO_HOME\u002Fbin`) to PATH for new terminals only. If `kraken` is not found right after install, call it by its full path, `~\u002F.cargo\u002Fbin\u002Fkraken` or `$CARGO_HOME\u002Fbin\u002Fkraken`, and\ntell the user to restart the agent from a new terminal window.\n\nVerify:\n\n```bash\nkraken --version && kraken-mcp --version\n```\n\n## 2. Start with paper trading\n\nPaper trading uses live prices with a simulated balance. No API keys required. Start here.\n\n```bash\nkraken workspace create sandbox --capital 10000 --mode paper -o json\nexport KRAKEN_WORKSPACE=sandbox\nkraken paper buy BTCUSD 0.01 -o json\nkraken workspace status -o json\n```\n\nFutures paper trading has one account that no workspace scopes, and it refuses\nchanges while a workspace is selected, so clear it first:\n\n```bash\nunset KRAKEN_WORKSPACE\nkraken futures paper init --balance 10000 -o json\nkraken futures paper buy PF_XBTUSD 1 --leverage 10 --type market -o json\nkraken futures paper positions -o json\n```\n\nPublic market data also needs no credentials:\n\n```bash\nkraken ticker BTCUSD -o json\nkraken orderbook BTCUSD --count 10 -o json\n```\n\nMost agent workflows can do their entire first session on paper and public data.\n\n## 3. (Optional) Add API credentials for live trading\n\nOnly needed if you want to query your real account or place real orders.\n\n### Recommended key scope\n\nGenerate the narrowest key you can live with. An AI agent should never be able to move funds off the exchange.\n\n- **Never enable `Withdraw Funds`.** Without this permission, even a prompt-injection or credential-exfiltration attack cannot remove assets from your Kraken account.\n- **Start read-only.** `Query Funds`, `Query Open Orders & Trades`, and `Query Closed Orders & Trades` are safe for a first session.\n- **Add trading scopes only when you need them.** `Create & Modify Orders` and `Cancel\u002FClose Orders` unlock live trading; no other scope is required for spot.\n- **Enable IP allowlisting if the agent runs from a static IP.** Kraken's API settings page lets you lock a key to one or more source IPs.\n- **Rotate on host change.** If you switch machines or re-install the plugin, revoke the old key and generate a new one.\n\nManage keys at \u003Chttps:\u002F\u002Fwww.kraken.com\u002Fu\u002Fsecurity\u002Fapi>.\n\n### Provide the key and secret to your agent\n\nThe CLI resolves credentials from three tiers, in order: command-line flags (`--api-key` \u002F `--api-secret`), environment variables (`KRAKEN_API_KEY` \u002F `KRAKEN_API_SECRET`), then the active stored key in a secure local config file managed by the CLI (stored with user-only permissions under your OS's standard config directory). The stored key is either the key from `kraken auth set` or `kraken setup`, or the sign-in key from `kraken auth login`; `kraken auth switch` selects which one. When an active sign-in key expires, private commands fail with an `auth` error and a hint to sign in again or switch. The CLI does not fall back to the other key. Pick the path that matches your client.\n\n#### Claude Code plugin\n\nThe `kraken-cli` plugin starts `kraken-mcp -s market,paper,feedback` and asks for no API key: none of those tools needs one. `kraken-mcp` still reads the active stored key from the CLI's local config, so a key saved earlier with `kraken auth set` or `kraken auth login` on the same machine is available to it. To keep the plugin credential-less, run `kraken auth reset` before starting Claude.\n\n#### Cursor, Codex, Gemini CLI\n\nLike the Claude plugin, these hosts start `kraken-mcp` with no key of their own. Either export credentials in the shell that launches the agent:\n\n```bash\nexport KRAKEN_API_KEY=\"your-key\"\nexport KRAKEN_API_SECRET=\"your-secret\"\n```\n\n…or rely on the key you stored with `kraken auth set` or `kraken auth login` — the plugin reads the same config file as the standalone CLI, so one stored key serves both, and `kraken auth switch` changes it for both.\n\nFor futures, use a Kraken Futures key and set `KRAKEN_FUTURES_API_KEY` and `KRAKEN_FUTURES_API_SECRET` alongside the spot pair, or store both pairs once with `kraken auth set --api-key \u003Cspot-key> --api-secret-file \u003Cspot-secret-file> --futures-api-key \u003Cfutures-key> --futures-api-secret-stdin` and let the config file supply them. `auth set` always saves the spot pair too, so `--api-key` is required.\n\n#### Plain CLI use (not through a plugin)\n\n`kraken auth set` writes credentials to a secure local config file managed by the CLI (stored with user-only permissions in your OS's standard config directory). `kraken auth login` instead signs you in through the browser and stores the Spot API key it creates there: no withdrawal permissions, and an expiry date (90 days unless `--valid-for` says otherwise). It needs a terminal, so a person runs it, never an agent. `kraken auth show` displays the stored keys masked as `****wxyz` and the secret as `[REDACTED]`, and names the key in use, so you can confirm which key signs without exposing it. `kraken auth reset` clears the stored credentials; a sign-in key stays valid on Kraken until it expires.\n\n### Verify\n\n```bash\nkraken balance -o json\n```\n\nNever commit these values. `.env` and `.env.*` are already gitignored in the repo.\n\n## 4. Connect an MCP client\n\nThe CLI ships with a built-in MCP server. Point any MCP-compatible client (Claude Code, Claude Desktop, Cursor, Codex, Gemini CLI, VS Code, Windsurf) at it.\n\nSee `skills\u002Fkraken-mcp-integration\u002FSKILL.md` for the per-client config blocks and the full service reference.\n\nThe default MCP config in every `kraken-cli` marketplace listing (Claude, Cursor, Codex, Gemini) is `-s market,paper,feedback`:\n\n| Service | Auth | Why it's in the default |\n|---------|------|-------------------------|\n| `market` | None | Public price data, orderbooks, OHLC. |\n| `paper`  | None | Simulated trading with live prices. |\n| `feedback` | None | Lets the agent report friction or bugs. It uploads the text it writes, or a local file it names, to Kraken with no approval step; drop it from `-s` for an agent that reads untrusted input. |\n\nA fresh install can never place a real order. Live trading is an explicit\nopt-in: widen the service list in your MCP client's config to `-s market,trade,paper`\n(adds live spot orders) or `-s all` (everything, including funding and earn).\nSee the service table and the \"Enabling live trading\" section in\n`skills\u002Fkraken-mcp-integration\u002FSKILL.md` for the complete list and recommended\nprogression.\n\n## 5. Safety defaults\n\n- Commands flagged `dangerous` in `agents\u002Ftool-catalog.json` require explicit user confirmation. MCP surfaces this via the `destructive_hint` annotation.\n- Always try `--validate` before submitting a spot order. Futures orders have no dry run, so test them on `kraken futures paper` first.\n- Run paper-first, live-second. `skills\u002Fkraken-paper-to-live\u002FSKILL.md` covers the promotion checklist.\n\n## Troubleshooting\n\n**`kraken: command not found`**: the install directory isn't on `$PATH` yet. Open a new terminal, or call `~\u002F.cargo\u002Fbin\u002Fkraken` (or `$CARGO_HOME\u002Fbin\u002Fkraken`) by its full path.\n\n**`auth` error on every command**: you exported a key with insufficient permissions. Regenerate with the scopes above.\n\n**Futures commands fail with `auth` but spot works**: futures needs its own key. Set `KRAKEN_FUTURES_API_KEY` and `KRAKEN_FUTURES_API_SECRET`.\n\n**MCP client shows no Kraken tools**: confirm `kraken-mcp` is on the PATH the client sees (MCP clients often start with a minimal environment), or set `command` to the absolute path that `command -v kraken-mcp` prints in a new terminal. Most clients start the server without a shell, so `~` and `$CARGO_HOME` stay unexpanded. Releases before this one installed `kraken` only: run the one-liner again. Then see `kraken-mcp-integration` troubleshooting.\n\nIf you hit a mismatch between what you are trying to do and the CLI's interface or responses — including a mismatch between this skill and the installed CLI version's contract — feel free to submit feedback with `kraken feedback`.\n",{"name":5,"version":49,"metadata":50,"description":7},"1.1.0",{"openclaw":51,"requires":52},{"category":36},{"bins":53},[31],"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fexchanges\u002Fkraken-official-kraken-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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill kraken-setup",{"tool":69,"command":70},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill kraken-setup",{"tool":72,"command":73},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill kraken-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-kraken-setup\u002FSKILL.md",true,[77,81,87],{"path":78,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":16},"LICENSE","许可证",1074,{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"SOURCE.md","REFERENCE","参考文档",337,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-kraken-setup\u002FSOURCE.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"TRUST.auto.yaml",2394,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fkraken-official-kraken-setup\u002FTRUST.auto.yaml",[92,120,142,160,173,183],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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.","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",[],[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"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},"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",[],[129,130,131,38,132,133,134,135,136,137,138,139,140,141],"mexc spot websocket","spot","websocket","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"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":124,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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",[],[150,130,151,152,153,154,155,139,138,137,156,157,158,133,159,132,38],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":124,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":167,"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",[],[168,169,131,170,171,140,138,172,136,135,133,132],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":174,"name":175,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":179,"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",[],[180,181,182],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":187,"sourceHtmlUrl":188,"categories":189,"keywords":190,"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",[],[191,192,193,194,195,196,197,198,199,200,201],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","use","patch","code","share"]