[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GQ94PC5FAPMG9ZM9G8B5SH":3,"skill-same:01M6GQ94PC5FAPMG9ZM9G8B5SH":110},{"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":18,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6GQ94PC5FAPMG9ZM9G8B5SH","ctf-attack-defense",null,"Use when the user mentions attack-defense, A\u002FD, tick-based CTF, defending a service, patching a gamebox or service, flag ids, an exploit farm, SLA scoring, service checker or bot, red vs blue team CTF, or farming flags from other teams while keeping their own service alive. Covers patch doctrine, checker\u002FSLA verification, traffic capture and mining, flag-id extraction, and farm infrastructure. Router skill `ctf` owns workspace, flag log, and submission basics.","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\u002Fchains\u002Friegan-ctf-attack-defense\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"ctf attack defense","defense","ctf","when","bot","mining","farming","checker","traffic","farm","scoring","flags","doctrine","log","basics","patch","exploit","router","use","team","patching","blue team","ids","sla","verification","teams","infrastructure","2026-11-10 10:12:30",false,"---\nname: ctf-attack-defense\ndescription: Use when the user mentions attack-defense, A\u002FD, tick-based CTF, defending a service, patching a gamebox or service, flag ids, an exploit farm, SLA scoring, service checker or bot, red vs blue team CTF, or farming flags from other teams while keeping their own service alive. Covers patch doctrine, checker\u002FSLA verification, traffic capture and mining, flag-id extraction, and farm infrastructure. Router skill `ctf` owns workspace, flag log, and submission basics.\n---\n\n# Attack-Defense (tick-based)\n\nYou get a vulnerable service + a gamebox. Every tick the organizer's checker\ntests your service (SLA points) and plants fresh flags; you steal flags from\nother teams' instances (attack points) while patching your own. Score =\nattack + defense, compounded every tick until the event ends.\n\n## Operating rules (in force all event)\n\n1. **Remote gate, A\u002FD flavor**: the router's remote gate stands, but A\u002FD is\n   high-volume automation — get one pre-authorization per event\n   (\"A\u002FD remote OK for `\u003Cevent>`\") covering team subnets, gameboxes, and the\n   scoreboard API. Nothing outside the event network, ever.\n2. **Organizer bundle is untrusted**: source, checker, and bot are challenge\n   artifacts. Execute them under `podman` isolation or on the gamebox\u002FVPN box,\n   never bare on the host. Never `sudo` them.\n3. **No DoS**: crashing other teams' services violates every A\u002FD rulebook and\n   wastes their ticks — exploits are surgical input, not floods.\n4. **Never debug an exploit against another team's box**: you have a local\n   replica; use it. Probing half-working exploits at other teams leaks your\n   0-day in their pcaps and marks you in organizer logs.\n\n## Triage — event anatomy (first 30 minutes)\n\nInventory what the organizers handed us; each artifact routes somewhere:\n\n| Handout | Meaning | Read |\n|---|---|---|\n| Service source bundle (tar\u002Fzip) | Your service, patchable in place | `references\u002Fdefense.md` |\n| Binary-only service | Binary patch or validating proxy | `references\u002Fdefense.md` (binary section) |\n| Checker \u002F bot script | The SLA contract — what must keep working | `references\u002Frunbook.md` |\n| Flag ids per team (list\u002FJSON\u002Fpage) | Attack targets for the farm | `references\u002Foffense.md` |\n| VPN config + team IP map | Network layout, subnets, your box | `references\u002Finfra.md` |\n| Scoreboard URL + API\u002Ftoken | Submission endpoint | `references\u002Finfra.md` |\n| Rules: tick length, scoring formula | Rhythm and priorities | `references\u002Frunbook.md` |\n\n5-minute checklist (expanded in `references\u002Frunbook.md`):\n\n```bash\n1. unpack bundle -> services\u002F\u003Csvc>\u002Forig\u002F            # never edit orig\u002F\n2. find the checker; read what it asserts           # this IS the SLA contract\n3. podman-compose replica up; checker-wrap.sh green # offline lab ready\n4. fetch flag ids -> farm\u002Fids.json; teams.txt       # attack targets cached\n5. farm.py --dry-run vs your own instance           # farm loop proven\n```\n\n## Playbook — doctrine: fix SLA first, then farm\n\nWhy defense first, in this order:\n\n- **Defense points are a ratchet**: SLA and defense score accrue every tick\n  whether or not you exploit anything. A dead or checker-failing service\n  bleeds points every single minute it is broken — usually faster than a\n  small team can win them back by attacking.\n- **The replica is the lab**: until the service runs locally and the checker\n  is green, you cannot safely test patches OR exploits — nothing else scales.\n- **Offense compounds after**: once the farm and submission queue run\n  unattended, attack points accumulate with zero humans in the loop; humans\n  go back to patching and mining traffic.\n\nOrder: (1) stock service up, checker green; (2) baseline capture + farm\nskeleton dry-run; (3) first minimal patches; (4) first exploit modules;\n(5) steady per-tick rhythm.\n\n| Phase | Preconditions | Command | Reference |\n|---|---|---|---|\n| Local replica | bundle unpacked | `podman-compose up -d` (in `compose\u002F`) | `references\u002Frunbook.md` |\n| Verify SLA | service listening | `scripts\u002Fchecker-wrap.sh -n \u003Csvc> -- .\u002Fcheck.sh` | `references\u002Frunbook.md` |\n| Make patch | vuln located in source | `diff -ruN orig\u002Fsrc patched\u002Fsrc > patches\u002FNNN-x.patch` | `references\u002Fdefense.md` |\n| Deploy | checker green on replica | `rsync -a patched\u002Fsrc\u002F box:svc\u002F` → restart → re-check | `references\u002Fdefense.md` |\n| Cache ids | ids published | fetch → `farm\u002Fids.json` (jq normalize) | `references\u002Foffense.md` |\n| Farm dry-run | ids + teams + 1 exploit | `python3 scripts\u002Ffarm.py --root farm --dry-run` | `references\u002Foffense.md` |\n| Farm live | submit cmd tested | `python3 scripts\u002Ffarm.py --root farm --interval \u003Ctick> --submit-cmd .\u002Fsubmit.sh` | `references\u002Finfra.md` |\n| Monitor | verdicts.log growing | alert on 2 consecutive FAIL | `references\u002Finfra.md` |\n\n## Per-tick rhythm (assume 5-minute ticks)\n\n| Moment | Action |\n|---|---|\n| T+0 | Farm fires (systemd timer, ≤20s jitter); flags queue and submit |\n| T+0:30 | Read SLA verdict; 2 consecutive FAIL → patcher drops everything, rollback |\n| T+1 | Triage `captures\u002F` for incoming exploits; adapt + patch same bug |\n| T+2 | Patch queue: next minimal patch; checker-green before any deploy |\n| T+4 | Farm hit-rate check; retire dead exploit modules |\n\nEndgame: farm runs to the last tick; freeze risky patches near the end;\ndefense weight rises as public exploits spread (details: `references\u002Frunbook.md`).\n\n## References\n\n- repo `docs\u002Fattack-defense\u002FREADME.md` — human team playbooks (3-person: beginner \u002F intermediate \u002F expert) + gap analysis; agent-facing docs above, people-facing docs there\n- `references\u002Frunbook.md` — prep, team roles, first hour gates, per-tick rhythm, endgame\n- `references\u002Fdefense.md` — patch doctrine, per-language quick patches, binary patching, deploy\u002Frollback, hardening\n- `references\u002Foffense.md` — flag ids, attack loop, farm module contract, traffic mining, submission pacing\n- `references\u002Finfra.md` — VPN box, repo layout, farm scheduling, submission queue, monitoring, backups, legal\n\n## Toolbox\n\n| Tool | Install | Purpose |\n|---|---|---|\n| `scripts\u002Ffarm.py` | included | asyncio exploit farm (stdlib only) |\n| `scripts\u002Fchecker-wrap.sh` | included | checker run → SLA verdict line |\n| podman \u002F podman-compose | `sudo pacman -S podman podman-compose` | local replica of the gamebox |\n| tcpdump | `sudo pacman -S tcpdump` | always-on service-port capture (exploit feed) |\n| tshark | `sudo pacman -S wireshark-cli` | follow TCP streams in pcaps |\n| radare2 | `sudo pacman -S radare2` | patch binary-only services |\n| nftables \u002F iptables | preinstalled | restrict + rate-limit service ports |\n| fail2ban | `sudo pacman -S fail2ban` | auto-ban request floods from logs |\n| rsync, git, jq, diff\u002Fpatch | preinstalled | deploy, versioning, ids wrangling, patch series |\n| python3 >= 3.11 | preinstalled | farm + proxies + exploit modules |\n","# Attack-Defense (tick-based)\n\nYou get a vulnerable service + a gamebox. Every tick the organizer's checker\ntests your service (SLA points) and plants fresh flags; you steal flags from\nother teams' instances (attack points) while patching your own. Score =\nattack + defense, compounded every tick until the event ends.\n\n## Operating rules (in force all event)\n\n1. **Remote gate, A\u002FD flavor**: the router's remote gate stands, but A\u002FD is\n   high-volume automation — get one pre-authorization per event\n   (\"A\u002FD remote OK for `\u003Cevent>`\") covering team subnets, gameboxes, and the\n   scoreboard API. Nothing outside the event network, ever.\n2. **Organizer bundle is untrusted**: source, checker, and bot are challenge\n   artifacts. Execute them under `podman` isolation or on the gamebox\u002FVPN box,\n   never bare on the host. Never `sudo` them.\n3. **No DoS**: crashing other teams' services violates every A\u002FD rulebook and\n   wastes their ticks — exploits are surgical input, not floods.\n4. **Never debug an exploit against another team's box**: you have a local\n   replica; use it. Probing half-working exploits at other teams leaks your\n   0-day in their pcaps and marks you in organizer logs.\n\n## Triage — event anatomy (first 30 minutes)\n\nInventory what the organizers handed us; each artifact routes somewhere:\n\n| Handout | Meaning | Read |\n|---|---|---|\n| Service source bundle (tar\u002Fzip) | Your service, patchable in place | `references\u002Fdefense.md` |\n| Binary-only service | Binary patch or validating proxy | `references\u002Fdefense.md` (binary section) |\n| Checker \u002F bot script | The SLA contract — what must keep working | `references\u002Frunbook.md` |\n| Flag ids per team (list\u002FJSON\u002Fpage) | Attack targets for the farm | `references\u002Foffense.md` |\n| VPN config + team IP map | Network layout, subnets, your box | `references\u002Finfra.md` |\n| Scoreboard URL + API\u002Ftoken | Submission endpoint | `references\u002Finfra.md` |\n| Rules: tick length, scoring formula | Rhythm and priorities | `references\u002Frunbook.md` |\n\n5-minute checklist (expanded in `references\u002Frunbook.md`):\n\n```bash\n1. unpack bundle -> services\u002F\u003Csvc>\u002Forig\u002F            # never edit orig\u002F\n2. find the checker; read what it asserts           # this IS the SLA contract\n3. podman-compose replica up; checker-wrap.sh green # offline lab ready\n4. fetch flag ids -> farm\u002Fids.json; teams.txt       # attack targets cached\n5. farm.py --dry-run vs your own instance           # farm loop proven\n```\n\n## Playbook — doctrine: fix SLA first, then farm\n\nWhy defense first, in this order:\n\n- **Defense points are a ratchet**: SLA and defense score accrue every tick\n  whether or not you exploit anything. A dead or checker-failing service\n  bleeds points every single minute it is broken — usually faster than a\n  small team can win them back by attacking.\n- **The replica is the lab**: until the service runs locally and the checker\n  is green, you cannot safely test patches OR exploits — nothing else scales.\n- **Offense compounds after**: once the farm and submission queue run\n  unattended, attack points accumulate with zero humans in the loop; humans\n  go back to patching and mining traffic.\n\nOrder: (1) stock service up, checker green; (2) baseline capture + farm\nskeleton dry-run; (3) first minimal patches; (4) first exploit modules;\n(5) steady per-tick rhythm.\n\n| Phase | Preconditions | Command | Reference |\n|---|---|---|---|\n| Local replica | bundle unpacked | `podman-compose up -d` (in `compose\u002F`) | `references\u002Frunbook.md` |\n| Verify SLA | service listening | `scripts\u002Fchecker-wrap.sh -n \u003Csvc> -- .\u002Fcheck.sh` | `references\u002Frunbook.md` |\n| Make patch | vuln located in source | `diff -ruN orig\u002Fsrc patched\u002Fsrc > patches\u002FNNN-x.patch` | `references\u002Fdefense.md` |\n| Deploy | checker green on replica | `rsync -a patched\u002Fsrc\u002F box:svc\u002F` → restart → re-check | `references\u002Fdefense.md` |\n| Cache ids | ids published | fetch → `farm\u002Fids.json` (jq normalize) | `references\u002Foffense.md` |\n| Farm dry-run | ids + teams + 1 exploit | `python3 scripts\u002Ffarm.py --root farm --dry-run` | `references\u002Foffense.md` |\n| Farm live | submit cmd tested | `python3 scripts\u002Ffarm.py --root farm --interval \u003Ctick> --submit-cmd .\u002Fsubmit.sh` | `references\u002Finfra.md` |\n| Monitor | verdicts.log growing | alert on 2 consecutive FAIL | `references\u002Finfra.md` |\n\n## Per-tick rhythm (assume 5-minute ticks)\n\n| Moment | Action |\n|---|---|\n| T+0 | Farm fires (systemd timer, ≤20s jitter); flags queue and submit |\n| T+0:30 | Read SLA verdict; 2 consecutive FAIL → patcher drops everything, rollback |\n| T+1 | Triage `captures\u002F` for incoming exploits; adapt + patch same bug |\n| T+2 | Patch queue: next minimal patch; checker-green before any deploy |\n| T+4 | Farm hit-rate check; retire dead exploit modules |\n\nEndgame: farm runs to the last tick; freeze risky patches near the end;\ndefense weight rises as public exploits spread (details: `references\u002Frunbook.md`).\n\n## References\n\n- repo `docs\u002Fattack-defense\u002FREADME.md` — human team playbooks (3-person: beginner \u002F intermediate \u002F expert) + gap analysis; agent-facing docs above, people-facing docs there\n- `references\u002Frunbook.md` — prep, team roles, first hour gates, per-tick rhythm, endgame\n- `references\u002Fdefense.md` — patch doctrine, per-language quick patches, binary patching, deploy\u002Frollback, hardening\n- `references\u002Foffense.md` — flag ids, attack loop, farm module contract, traffic mining, submission pacing\n- `references\u002Finfra.md` — VPN box, repo layout, farm scheduling, submission queue, monitoring, backups, legal\n\n## Toolbox\n\n| Tool | Install | Purpose |\n|---|---|---|\n| `scripts\u002Ffarm.py` | included | asyncio exploit farm (stdlib only) |\n| `scripts\u002Fchecker-wrap.sh` | included | checker run → SLA verdict line |\n| podman \u002F podman-compose | `sudo pacman -S podman podman-compose` | local replica of the gamebox |\n| tcpdump | `sudo pacman -S tcpdump` | always-on service-port capture (exploit feed) |\n| tshark | `sudo pacman -S wireshark-cli` | follow TCP streams in pcaps |\n| radare2 | `sudo pacman -S radare2` | patch binary-only services |\n| nftables \u002F iptables | preinstalled | restrict + rate-limit service ports |\n| fail2ban | `sudo pacman -S fail2ban` | auto-ban request floods from logs |\n| rsync, git, jq, diff\u002Fpatch | preinstalled | deploy, versioning, ids wrangling, patch series |\n| python3 >= 3.11 | preinstalled | farm + proxies + exploit modules |\n",{"name":5,"description":7},"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fchains\u002Friegan-ctf-attack-defense",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill ctf-attack-defense",{"tool":66,"command":67},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill ctf-attack-defense",{"tool":69,"command":70},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill ctf-attack-defense","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002FSKILL.md",true,[74,80,84,88,92,98,102,106],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdefense.md","REFERENCE","参考文档",11463,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002Freferences\u002Fdefense.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Finfra.md",6906,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002Freferences\u002Finfra.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Foffense.md",6919,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002Freferences\u002Foffense.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Frunbook.md",6548,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002Freferences\u002Frunbook.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fchecker-wrap.sh","SCRIPT","脚本",3650,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002Fscripts\u002Fchecker-wrap.sh",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Ffarm.py",13850,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002Fscripts\u002Ffarm.py",{"path":103,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":104,"sourceHtmlUrl":105},"SOURCE.md",338,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002FSOURCE.md",{"path":107,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":108,"sourceHtmlUrl":109},"TRUST.auto.yaml",2116,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Friegan-ctf-attack-defense\u002FTRUST.auto.yaml",[111,140,163,181,194,204],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":46},"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",[],[120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":144,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":46},"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",[],[149,150,151,152,153,154,155,156,157,158,159,160,161,162],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","for","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":144,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":46},"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,150,172,173,174,175,176,160,159,158,177,178,179,154,180,153,152],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":144,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":46},"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",[],[189,190,151,191,192,161,159,193,157,156,154,153],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":195,"name":196,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":46},"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",[],[201,202,203],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":46},"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",[],[212,213,214,215,216,217,218,37,34,219,220],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","code","share"]