[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GS6YRAXFWBBG2VRHM3V6BJ":3,"skill-same:01M6GS6YRAXFWBBG2VRHM3V6BJ":93},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6GS6YRAXFWBBG2VRHM3V6BJ","crypto-paper-review",null,"Use when pre-reviewing, peer reviewing, stress-testing, or assessing submission readiness of a cryptography, ZKP, lattice, or security paper for a leading research venue.","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\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002FSKILL.md",[19],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"review","crypto paper review","paper review","paper","crypto","zkp","use","peer","cryptography","research","readiness","lattice","stress","security","testing","for","submission","when","2026-11-10 10:12:30",false,"---\nname: crypto-paper-review\ndescription: Use when pre-reviewing, peer reviewing, stress-testing, or assessing submission readiness of a cryptography, ZKP, lattice, or security paper for a leading research venue.\n---\n\n# Crypto Paper Review\n\nPerform an adversarial, evidence-located review. Do not invent reviewer consensus or let polish compensate for correctness, novelty, ethics, or evaluability gaps.\n\n## Scope\n\nIn scope: venue fit, contribution\u002Fsignificance, novelty\u002Fprior art, definitions\u002Ftheorems\u002Fproofs\u002Freductions, ZKP\u002Flattice specifics, parameters\u002Fcomplexity, experiments\u002Fartifacts, clarity, ethics\u002Fdisclosure\u002Fopen science, reproducibility, and revision priority.\n\nOut of scope: actual PC decisions, hidden-reviewer knowledge, fabricated independent reviewers, or rewriting without request.\n\n## Required Inputs\n\n- exact manuscript\u002Fversion and supplements\u002Fartifacts;\n- target venue and current official policies, if venue-specific;\n- claimed contributions and evidence map when available;\n- desired mode: quick triage, full review, methodology\u002Fproof focus, or re-review.\n\n## Success Criteria\n\n- Every major claim is tested against evidence and closest-work context.\n- Findings cite exact manuscript\u002Fartifact locations and consequences.\n- Correctness, novelty, significance, evidence, reproducibility, clarity, ethics, and policy compliance are independent dimensions.\n- ZKP\u002Flattice\u002Fsecurity-model and parameter\u002Fcomplexity category errors are checked.\n- Blocking, major, and minor findings have concrete resolution\u002Fevidence requirements.\n- Verdict is calibrated as readiness\u002Frisk, not a predicted or fabricated conference decision.\n- A re-review verifies each claimed repair and detects regressions.\n\n## Failure Modes\n\n- Missing manuscript\u002Fartifact\u002Fversion: limit review and mark unseen evidence.\n- Unknown venue policy: give venue-neutral review; do not claim compliance.\n- Citation\u002Ffull proof inaccessible: keep dependent claims unverified.\n- Same-agent multi-perspective pass: label it non-independent.\n- Manuscript advocacy pressure: preserve disconfirming findings.\n\nNever fabricate citations, proof checks, artifact runs, reviewer opinions, scores, or acceptance probabilities.\n\n## Workflow\n\n1. Apply [protocol.md](references\u002Fprotocol.md) to freeze claims\u002Fevidence and target-venue gates.\n2. Run sequential lenses: fit\u002Fsignificance; novelty; correctness\u002Fsecurity; parameters\u002Fevidence; reproducibility\u002Fethics; exposition\u002Fadversarial challenge.\n3. Consolidate duplicate findings without erasing disagreement or uncertainty.\n4. Return severity-ranked report, readiness verdict, and revision plan.\n5. In re-review, map each prior finding to exact changed evidence.\n6. Use [evaluation-scenarios.md](references\u002Fevaluation-scenarios.md) for future independent evaluation.\n\n## Output Contract\n\nReturn: scope\u002Fversion\u002Fpolicy snapshot; paper and contribution summary; strengths; blocking\u002Fmajor\u002Fminor findings with locations; claim-evidence and domain audits; novelty\u002Fclosest-work risks; artifact\u002Fethics\u002Fcompliance risks; questions to authors; readiness verdict; ordered revision plan; unverified items.\n\n","# Crypto Paper Review\n\nPerform an adversarial, evidence-located review. Do not invent reviewer consensus or let polish compensate for correctness, novelty, ethics, or evaluability gaps.\n\n## Scope\n\nIn scope: venue fit, contribution\u002Fsignificance, novelty\u002Fprior art, definitions\u002Ftheorems\u002Fproofs\u002Freductions, ZKP\u002Flattice specifics, parameters\u002Fcomplexity, experiments\u002Fartifacts, clarity, ethics\u002Fdisclosure\u002Fopen science, reproducibility, and revision priority.\n\nOut of scope: actual PC decisions, hidden-reviewer knowledge, fabricated independent reviewers, or rewriting without request.\n\n## Required Inputs\n\n- exact manuscript\u002Fversion and supplements\u002Fartifacts;\n- target venue and current official policies, if venue-specific;\n- claimed contributions and evidence map when available;\n- desired mode: quick triage, full review, methodology\u002Fproof focus, or re-review.\n\n## Success Criteria\n\n- Every major claim is tested against evidence and closest-work context.\n- Findings cite exact manuscript\u002Fartifact locations and consequences.\n- Correctness, novelty, significance, evidence, reproducibility, clarity, ethics, and policy compliance are independent dimensions.\n- ZKP\u002Flattice\u002Fsecurity-model and parameter\u002Fcomplexity category errors are checked.\n- Blocking, major, and minor findings have concrete resolution\u002Fevidence requirements.\n- Verdict is calibrated as readiness\u002Frisk, not a predicted or fabricated conference decision.\n- A re-review verifies each claimed repair and detects regressions.\n\n## Failure Modes\n\n- Missing manuscript\u002Fartifact\u002Fversion: limit review and mark unseen evidence.\n- Unknown venue policy: give venue-neutral review; do not claim compliance.\n- Citation\u002Ffull proof inaccessible: keep dependent claims unverified.\n- Same-agent multi-perspective pass: label it non-independent.\n- Manuscript advocacy pressure: preserve disconfirming findings.\n\nNever fabricate citations, proof checks, artifact runs, reviewer opinions, scores, or acceptance probabilities.\n\n## Workflow\n\n1. Apply [protocol.md](references\u002Fprotocol.md) to freeze claims\u002Fevidence and target-venue gates.\n2. Run sequential lenses: fit\u002Fsignificance; novelty; correctness\u002Fsecurity; parameters\u002Fevidence; reproducibility\u002Fethics; exposition\u002Fadversarial challenge.\n3. Consolidate duplicate findings without erasing disagreement or uncertainty.\n4. Return severity-ranked report, readiness verdict, and revision plan.\n5. In re-review, map each prior finding to exact changed evidence.\n6. Use [evaluation-scenarios.md](references\u002Fevaluation-scenarios.md) for future independent evaluation.\n\n## Output Contract\n\nReturn: scope\u002Fversion\u002Fpolicy snapshot; paper and contribution summary; strengths; blocking\u002Fmajor\u002Fminor findings with locations; claim-evidence and domain audits; novelty\u002Fclosest-work risks; artifact\u002Fethics\u002Fcompliance risks; questions to authors; readiness verdict; ordered revision plan; unverified items.\n\n",{"name":5,"description":7},"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fdev-tools\u002Friaomike-crypto-paper-review",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill crypto-paper-review",{"tool":63,"command":64},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill crypto-paper-review",{"tool":66,"command":67},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill crypto-paper-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002FSKILL.md",true,[71,75,81,85,89],{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fevaluation-scenarios.md","REFERENCE","参考文档",960,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002Freferences\u002Fevaluation-scenarios.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fprotocol.md",2527,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002Freferences\u002Fprotocol.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"SOURCE.md",381,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002FSOURCE.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-paper-review\u002FTRUST.auto.yaml",[94,122,144,162,175,185],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":43},"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",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":43},"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",[],[131,132,133,134,135,136,137,138,139,140,40,141,142,143],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":43},"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",[],[152,132,153,154,155,156,157,141,40,140,158,159,160,136,161,135,134],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":126,"licenseFileUrl":166,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":43},"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",[],[170,171,133,172,173,142,40,174,139,138,136,135],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":176,"name":177,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":178,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":43},"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",[],[182,183,184],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":43},"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",[],[193,194,195,196,197,198,199,31,200,201,202],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]