[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GRQ7FEF6AH8A7VR1X4DSP7":3,"skill-same:01M6GRQ7FEF6AH8A7VR1X4DSP7":92},{"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":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6GRQ7FEF6AH8A7VR1X4DSP7","polish-writing",null,"Use for a final language pass on a paper section, or when translating a Chinese draft into English academic prose. Removes AI-sounding phrasing, tightens sentences, enforces consistent notation and terminology, and never changes numbers, claims or LaTeX semantics.","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\u002Facprk-polish-writing\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Facprk-polish-writing\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"polish","polish writing","writing","Academic","when","section","changes","for","claims","notation","english","paper","draft","terminology","chinese","language","prose","never","use","LaTeX","2026-11-10 10:12:30",false,"---\nname: polish-writing\ndescription: Use for a final language pass on a paper section, or when translating a Chinese draft into English academic prose. Removes AI-sounding phrasing, tightens sentences, enforces consistent notation and terminology, and never changes numbers, claims or LaTeX semantics.\n---\n\n# Polish writing\n\n## Invariants (never violate)\n\n- Do not change numbers, theorem statements, hypotheses, citations, labels or math.\n- Do not strengthen claims (\"shows\" → \"proves\", \"up to\" → \"always\").\n- Keep LaTeX commands intact; do not introduce packages.\n- In the last 24 hours before a deadline: no style passes at all, only error fixes.\n- Output: revised text + a short modification log (what and why) so the author can\n  accept\u002Freject each change.\n\n## Pass 1 — de-AI\n\nReplace or delete:\n\n| avoid | prefer |\n|---|---|\n| leverage, utilize | use |\n| delve into, explore (as a result) | examine, study (or state the result) |\n| pivotal, crucial, paramount | important, key (or delete) |\n| underscore, highlight (as filler) | show |\n| tapestry, landscape, realm | (delete; name the area) |\n| seamless(ly), robust (without a metric) | (delete or quantify) |\n| \"It is worth noting that\", \"Notably,\" | (delete; state the fact) |\n| \"In this paper, we aim to\" | \"We ...\" |\n| \"First and foremost\", \"Last but not least\" | (delete) |\n| \"plays a crucial role in\" | \"determines\", \"dominates\" (be specific) |\n| \"novel\" about own work | (delete; let the reader judge) |\n| \"significantly\" without numbers | the number |\n| \"obviously\", \"it is easy to see\" | give the one-line reason, or delete |\n\nAlso: convert `itemize` inside running text into connected prose when the items are\nreasoning steps (keep lists for contributions\u002Fparameters); avoid three connectives\nin a row; vary sentence openings; no rhetorical questions in the body.\n\n## Pass 2 — concision\n\n- One idea per sentence; aim for ≤ 30 words.\n- Remove throat-clearing openers and doubled phrases (\"in order to\" → \"to\",\n  \"the fact that\" → \"that\", \"a number of\" → \"several\"\u002Fthe number).\n- Prefer verbs over nominalisations (\"perform an evaluation of\" → \"evaluate\").\n- Active voice for what *we* did; passive is fine for standard facts.\n- Avoid dashes as sentence punctuation (use commas, colons, or split sentences).\n\n## Pass 3 — consistency\n\n- Terminology: one name per concept (framework name, stage names, baseline names).\n  Build a term list from the notation table and `grep` for variants\n  (e.g. \"bootstrap\"\u002F\"bootstrapping\", \"look-up table\"\u002F\"lookup table\", \"LUT\").\n- Notation: symbols match the notation table; no symbol reused with two meanings;\n  vectors\u002Fmatrices consistently bold or not.\n- Spelling variety: pick US or UK and stay with it.\n- Capitalisation of references: `Section~\\ref`, `Table~\\ref`, or `\\Cref` consistently;\n  non-breaking spaces before `\\cite` and `\\ref`.\n- Numbers: consistent units and precision (e.g. 2 significant digits for ratios);\n  `\\times` spacing consistent; thin space before units.\n\n## Pass 4 — Chinese → English (for drafts written in Chinese)\n\n1. Translate meaning, not word order: Chinese topic-comment sentences often become\n   English subject-verb sentences with the conclusion first.\n2. Split long Chinese sentences joined by commas (一逗到底) into several English\n   sentences.\n3. Watch for common calques: \"has important significance\" → \"matters because ...\";\n   \"realize\u002Fachieve an algorithm\" → \"implement\"; \"the proposed scheme\" repeated →\n   name it once, then \"our scheme\"\u002Fits name; \"in recent years\" as an opener → delete or\n   give the year range; \"greatly improve\" → the number.\n4. Articles: every singular countable noun needs a\u002Fthe; \"the\" for things already\n   introduced or unique (\"the bootstrapping procedure of [X]\").\n5. Tense: present for facts and what the paper does; past for what prior work did\n   or for experiments that were run.\n6. Produce three parts: `[LaTeX]` English text, `[Back-translation]` literal Chinese\n   of the English (so the author can check meaning), `[Log]` list of changes.\n\n## Pass 5 — read-aloud check\n\nRead the abstract and the first page aloud (or via TTS). Any sentence that needs a\nsecond breath gets split.\n","# Polish writing\n\n## Invariants (never violate)\n\n- Do not change numbers, theorem statements, hypotheses, citations, labels or math.\n- Do not strengthen claims (\"shows\" → \"proves\", \"up to\" → \"always\").\n- Keep LaTeX commands intact; do not introduce packages.\n- In the last 24 hours before a deadline: no style passes at all, only error fixes.\n- Output: revised text + a short modification log (what and why) so the author can\n  accept\u002Freject each change.\n\n## Pass 1 — de-AI\n\nReplace or delete:\n\n| avoid | prefer |\n|---|---|\n| leverage, utilize | use |\n| delve into, explore (as a result) | examine, study (or state the result) |\n| pivotal, crucial, paramount | important, key (or delete) |\n| underscore, highlight (as filler) | show |\n| tapestry, landscape, realm | (delete; name the area) |\n| seamless(ly), robust (without a metric) | (delete or quantify) |\n| \"It is worth noting that\", \"Notably,\" | (delete; state the fact) |\n| \"In this paper, we aim to\" | \"We ...\" |\n| \"First and foremost\", \"Last but not least\" | (delete) |\n| \"plays a crucial role in\" | \"determines\", \"dominates\" (be specific) |\n| \"novel\" about own work | (delete; let the reader judge) |\n| \"significantly\" without numbers | the number |\n| \"obviously\", \"it is easy to see\" | give the one-line reason, or delete |\n\nAlso: convert `itemize` inside running text into connected prose when the items are\nreasoning steps (keep lists for contributions\u002Fparameters); avoid three connectives\nin a row; vary sentence openings; no rhetorical questions in the body.\n\n## Pass 2 — concision\n\n- One idea per sentence; aim for ≤ 30 words.\n- Remove throat-clearing openers and doubled phrases (\"in order to\" → \"to\",\n  \"the fact that\" → \"that\", \"a number of\" → \"several\"\u002Fthe number).\n- Prefer verbs over nominalisations (\"perform an evaluation of\" → \"evaluate\").\n- Active voice for what *we* did; passive is fine for standard facts.\n- Avoid dashes as sentence punctuation (use commas, colons, or split sentences).\n\n## Pass 3 — consistency\n\n- Terminology: one name per concept (framework name, stage names, baseline names).\n  Build a term list from the notation table and `grep` for variants\n  (e.g. \"bootstrap\"\u002F\"bootstrapping\", \"look-up table\"\u002F\"lookup table\", \"LUT\").\n- Notation: symbols match the notation table; no symbol reused with two meanings;\n  vectors\u002Fmatrices consistently bold or not.\n- Spelling variety: pick US or UK and stay with it.\n- Capitalisation of references: `Section~\\ref`, `Table~\\ref`, or `\\Cref` consistently;\n  non-breaking spaces before `\\cite` and `\\ref`.\n- Numbers: consistent units and precision (e.g. 2 significant digits for ratios);\n  `\\times` spacing consistent; thin space before units.\n\n## Pass 4 — Chinese → English (for drafts written in Chinese)\n\n1. Translate meaning, not word order: Chinese topic-comment sentences often become\n   English subject-verb sentences with the conclusion first.\n2. Split long Chinese sentences joined by commas (一逗到底) into several English\n   sentences.\n3. Watch for common calques: \"has important significance\" → \"matters because ...\";\n   \"realize\u002Fachieve an algorithm\" → \"implement\"; \"the proposed scheme\" repeated →\n   name it once, then \"our scheme\"\u002Fits name; \"in recent years\" as an opener → delete or\n   give the year range; \"greatly improve\" → the number.\n4. Articles: every singular countable noun needs a\u002Fthe; \"the\" for things already\n   introduced or unique (\"the bootstrapping procedure of [X]\").\n5. Tense: present for facts and what the paper does; past for what prior work did\n   or for experiments that were run.\n6. Produce three parts: `[LaTeX]` English text, `[Back-translation]` literal Chinese\n   of the English (so the author can check meaning), `[Log]` list of changes.\n\n## Pass 5 — read-aloud check\n\nRead the abstract and the first page aloud (or via TTS). Any sentence that needs a\nsecond breath gets split.\n",{"name":5,"description":7},"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fdev-tools\u002Facprk-polish-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-12 02:28:42",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill polish-writing",{"tool":70,"command":71},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill polish-writing",{"tool":73,"command":74},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill polish-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Facprk-polish-writing\u002FSKILL.md",true,[78,82,88],{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",1092,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"SOURCE.md","REFERENCE","参考文档",355,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Facprk-polish-writing\u002FSOURCE.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fdev-tools\u002Facprk-polish-writing\u002FTRUST.auto.yaml",[93,121,143,161,174,184],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":50},"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",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":50},"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",[],[130,131,132,133,134,135,136,137,138,139,37,140,141,142],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":147,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":50},"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",[],[151,131,152,153,154,155,156,140,37,139,157,158,159,135,160,134,133],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":50},"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",[],[169,170,132,171,172,141,37,173,138,137,135,134],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":175,"name":176,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":50},"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",[],[181,182,183],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":50},"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",[],[192,193,194,195,196,197,198,48,199,200,201],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]