[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GS7N5EXS51MF3V7PB80JF7":3,"skill-same:01M6GS7N5EXS51MF3V7PB80JF7":112},{"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":35,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6GS7N5EXS51MF3V7PB80JF7","crypto-venue-paper-writing",null,"Use when drafting, restructuring, or polishing a cryptography paper for a specific top venue (CRYPTO, EUROCRYPT, ASIACRYPT, IEEE S&P, ACM CCS, USENIX Security, NDSS) or for CRYPTO\u002FLNCS-style submission, including venue structure, abstract compression, de-AI rewriting, double-blind compliance, and format checks.","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-venue-paper-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002FSKILL.md",[19,24,27,32],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":28,"categoryName":29,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":33,"categoryName":34,"taxonomyType":30,"taxonomyTypeDesc":31},"01JBSEEDCAT000000000000037","律师与法务",[36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"Paper Writing","crypto venue paper writing","crypto","paper","writing","style","drafting","when","ieee","submission","for","top","de-ai","CCS","de","structure","use","format","cryptography","compliance","compression","security","2026-11-10 10:12:30",false,"---\nname: crypto-venue-paper-writing\ndescription: Use when drafting, restructuring, or polishing a cryptography paper for a specific top venue (CRYPTO, EUROCRYPT, ASIACRYPT, IEEE S&P, ACM CCS, USENIX Security, NDSS) or for CRYPTO\u002FLNCS-style submission, including venue structure, abstract compression, de-AI rewriting, double-blind compliance, and format checks.\n---\n\n# Crypto Venue Paper Writing\n\nWrite for the venue, not in the abstract: every structural and stylistic decision is made against one named conference's current official call, template, page limit, and reviewing culture.\n\n## Scope\n\nIn scope: choosing a venue-specific structure and section budget; writing or compressing an abstract (four-part formula, hard word cap); drafting contribution bullets, comparison tables, and technical overviews; organizing related work by technique family; writing preliminaries, construction, security, experiments, and conclusion in venue register; applying a concrete de-AI rewriting checklist; verifying double-blind anonymity; checking LNCS\u002FACM\u002FIEEE\u002FUSENIX formatting and citation style; and running a pre-submission quality pass.\n\nOut of scope: inventing results, proofs, citations, or experiments; upgrading claim tiers; deciding novelty or authorship; guaranteeing acceptance; or submitting without human authorization.\n\n## Required Inputs\n\n- target venue and its current official call for papers (page limit, template, anonymity, ethics, AI-disclosure, artifact policy);\n- manuscript draft or outline to revise, or verified claims\u002Fevidence to write from;\n- comparison corpus for the related-work and comparison-table positioning;\n- LaTeX\u002FMarkdown sources and bibliography, or the venue template to set up.\n\n## Success Criteria\n\n- Abstract follows the four-part formula (strongest defensible claim first, parameters, key technique, concrete numbers) and stays within the venue word cap (CRYPTO\u002FLNCS practice: at most 250 words; fewer when the venue says so).\n- Structure matches the named venue's convention, not generic IMRAD: contributions bullets, comparison table, and technical overview appear in the introduction area for crypto venues.\n- Every contribution bullet and every concrete number in the abstract\u002Ftable has an addressable body section; wording is calibrated (proven vs claimed vs estimated vs open).\n- De-AI checklist passes: no vocabulary flags, no forced structures, no meta-narrative, no workflow self-reference, no synonym cycling, no unbounded superlatives.\n- Double-blind wording holds everywhere, including self-citations, acknowledgments, artifact links, and code identifiers.\n- Page limit, template, bibliography style, and current CFP requirements are verified against the venue's official site at execution time, not assumed from memory.\n\n## Failure Modes\n\n- Draft with no target venue or no verified CFP snapshot: return structure-neutral guidance and require the official call before format claims.\n- Claim or number without a body address or evidence anchor: expose it and block the affected sentence rather than smoothing it over.\n- AI-flavor prose that survives a first pass: run the grep-level checklist in [de-ai-and-style.md](references\u002Fde-ai-and-style.md) and rewrite, do not just flag.\n- Venue template\u002Fpage rules may have changed since training: verify the current official template and CFP; never rely on remembered page limits or style files.\n- De-identification gap (author names, institution, identifying repo): fix before any format pass.\n\n## Workflow\n\n1. Freeze the target venue and fetch its current official CFP and template (see [venue-structure.md](references\u002Fvenue-structure.md) for per-venue anchors).\n2. Decide the venue structure and section budget; map existing content onto it.\n3. Write or rewrite in dependency order: comparison table first, then technical overview, then abstract, then introduction framing, then body sections.\n4. Apply the de-AI and register rules from [de-ai-and-style.md](references\u002Fde-ai-and-style.md) to every section, including the abstract and conclusion.\n5. Run the pre-submission pass: number\u002Fbody consistency, claim tiers, citation integrity, double-blind scan, page budget, template compile.\n6. Use [evaluation-scenarios.md](references\u002Fevaluation-scenarios.md) for future independent evaluation.\n\n## Output Contract\n\nReturn: target-venue policy snapshot with date; structure and section budget; revised manuscript or section diffs; abstract word count and four-part coverage; de-AI checklist results; double-blind and format compliance report; unresolved items requiring the human author.\n\n## Reference Files\n\n| File | Contents |\n|------|----------|\n| `references\u002Fvenue-structure.md` | Venue-specific structure, abstract formula, page limits, template anchors |\n| `references\u002Fde-ai-and-style.md` | De-AI vocabulary\u002Fstructure\u002Fcontent red flags and sentence-level register rules |\n| `references\u002Fevaluation-scenarios.md` | Test specifications for independent evaluation |\n","# Crypto Venue Paper Writing\n\nWrite for the venue, not in the abstract: every structural and stylistic decision is made against one named conference's current official call, template, page limit, and reviewing culture.\n\n## Scope\n\nIn scope: choosing a venue-specific structure and section budget; writing or compressing an abstract (four-part formula, hard word cap); drafting contribution bullets, comparison tables, and technical overviews; organizing related work by technique family; writing preliminaries, construction, security, experiments, and conclusion in venue register; applying a concrete de-AI rewriting checklist; verifying double-blind anonymity; checking LNCS\u002FACM\u002FIEEE\u002FUSENIX formatting and citation style; and running a pre-submission quality pass.\n\nOut of scope: inventing results, proofs, citations, or experiments; upgrading claim tiers; deciding novelty or authorship; guaranteeing acceptance; or submitting without human authorization.\n\n## Required Inputs\n\n- target venue and its current official call for papers (page limit, template, anonymity, ethics, AI-disclosure, artifact policy);\n- manuscript draft or outline to revise, or verified claims\u002Fevidence to write from;\n- comparison corpus for the related-work and comparison-table positioning;\n- LaTeX\u002FMarkdown sources and bibliography, or the venue template to set up.\n\n## Success Criteria\n\n- Abstract follows the four-part formula (strongest defensible claim first, parameters, key technique, concrete numbers) and stays within the venue word cap (CRYPTO\u002FLNCS practice: at most 250 words; fewer when the venue says so).\n- Structure matches the named venue's convention, not generic IMRAD: contributions bullets, comparison table, and technical overview appear in the introduction area for crypto venues.\n- Every contribution bullet and every concrete number in the abstract\u002Ftable has an addressable body section; wording is calibrated (proven vs claimed vs estimated vs open).\n- De-AI checklist passes: no vocabulary flags, no forced structures, no meta-narrative, no workflow self-reference, no synonym cycling, no unbounded superlatives.\n- Double-blind wording holds everywhere, including self-citations, acknowledgments, artifact links, and code identifiers.\n- Page limit, template, bibliography style, and current CFP requirements are verified against the venue's official site at execution time, not assumed from memory.\n\n## Failure Modes\n\n- Draft with no target venue or no verified CFP snapshot: return structure-neutral guidance and require the official call before format claims.\n- Claim or number without a body address or evidence anchor: expose it and block the affected sentence rather than smoothing it over.\n- AI-flavor prose that survives a first pass: run the grep-level checklist in [de-ai-and-style.md](references\u002Fde-ai-and-style.md) and rewrite, do not just flag.\n- Venue template\u002Fpage rules may have changed since training: verify the current official template and CFP; never rely on remembered page limits or style files.\n- De-identification gap (author names, institution, identifying repo): fix before any format pass.\n\n## Workflow\n\n1. Freeze the target venue and fetch its current official CFP and template (see [venue-structure.md](references\u002Fvenue-structure.md) for per-venue anchors).\n2. Decide the venue structure and section budget; map existing content onto it.\n3. Write or rewrite in dependency order: comparison table first, then technical overview, then abstract, then introduction framing, then body sections.\n4. Apply the de-AI and register rules from [de-ai-and-style.md](references\u002Fde-ai-and-style.md) to every section, including the abstract and conclusion.\n5. Run the pre-submission pass: number\u002Fbody consistency, claim tiers, citation integrity, double-blind scan, page budget, template compile.\n6. Use [evaluation-scenarios.md](references\u002Fevaluation-scenarios.md) for future independent evaluation.\n\n## Output Contract\n\nReturn: target-venue policy snapshot with date; structure and section budget; revised manuscript or section diffs; abstract word count and four-part coverage; de-AI checklist results; double-blind and format compliance report; unresolved items requiring the human author.\n\n## Reference Files\n\n| File | Contents |\n|------|----------|\n| `references\u002Fvenue-structure.md` | Venue-specific structure, abstract formula, page limits, template anchors |\n| `references\u002Fde-ai-and-style.md` | De-AI vocabulary\u002Fstructure\u002Fcontent red flags and sentence-level register rules |\n| `references\u002Fevaluation-scenarios.md` | Test specifications for independent evaluation |\n",{"name":5,"description":7},"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing",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-13 02:31:19",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill crypto-venue-paper-writing",{"tool":78,"command":79},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill crypto-venue-paper-writing",{"tool":81,"command":82},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill crypto-venue-paper-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002FSKILL.md",true,[86,90,96,100,104,108],{"path":87,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":16},"LICENSE","许可证",1067,{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fde-ai-and-style.md","REFERENCE","参考文档",5204,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002Freferences\u002Fde-ai-and-style.md",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fevaluation-scenarios.md",1218,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002Freferences\u002Fevaluation-scenarios.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fvenue-structure.md",4476,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002Freferences\u002Fvenue-structure.md",{"path":105,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":106,"sourceHtmlUrl":107},"SOURCE.md",388,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002FSOURCE.md",{"path":109,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":110,"sourceHtmlUrl":111},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Friaomike-crypto-venue-paper-writing\u002FTRUST.auto.yaml",[113,141,163,181,194,204],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":58},"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",[],[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":145,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":58},"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",[],[150,151,152,153,154,155,156,157,158,159,46,160,161,162],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":145,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":58},"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,151,172,173,174,175,176,160,46,159,177,178,179,155,180,154,153],"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":145,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":58},"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,152,191,192,161,46,193,158,157,155,154],"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":15,"licenseFileUrl":197,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":58},"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":15,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":58},"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,52,219,220,221],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]