[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H3AX6XYFXEYSJXRYFBP902":3,"skill-same:01M6H3AX6XYFXEYSJXRYFBP902":88},{"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":19,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6H3AX6XYFXEYSJXRYFBP902","profiling-regression-proposal",null,"Proposes follow-up actions for an already-classified Hermes CPU-profile regression using only the profiling evidence supplied by the caller. Use after deterministic tooling has identified a slow scenario and correlated hot-frame paths with files from recently merged pull requests.","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\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"regression","profiling","proposal","profiling regression proposal","files","frame","for","requests","with","CPU","paths","scenario","deterministic","pull requests","tooling","up","evidence","only","use","actions","pull","2026-11-10 10:12:30",false,"---\nname: profiling-regression-proposal\ndescription: >-\n  Proposes follow-up actions for an already-classified Hermes CPU-profile\n  regression using only the profiling evidence supplied by the caller. Use\n  after deterministic tooling has identified a slow scenario and correlated\n  hot-frame paths with files from recently merged pull requests.\nmaturity: stable\n---\n\n# Profiling Regression Proposal\n\nProduce a short, evidence-bound proposal after deterministic profiling tooling\nhas already classified a run. This skill interprets evidence; it does not decide\nwhether a regression exists.\n\n## When To Use\n\nUse this skill only when the caller supplies structured evidence containing:\n\n- findings produced by a deterministic threshold;\n- hot frames extracted from generated CPU-profile reports;\n- recently merged pull requests separated by whether their changed files\n  overlap those hot-frame paths.\n\nDo not use source-tree searches, repository knowledge, issue history, PR titles,\nor general performance heuristics as additional evidence.\n\n## Workflow\n\n1. Treat the supplied evidence object as the only source of truth.\n2. Do not change, second-guess, or reapply the caller's regression threshold.\n3. Mention a file, function, timing, ratio, run, or owner only when it appears\n   in the evidence.\n4. Connect a pull request to a finding only when the caller places it in the\n   profile-overlap collection. A title that mentions the affected feature is\n   not evidence.\n5. A changed file may be discussed only when its path already occurs in a hot\n   frame from the generated profile.\n6. Pull requests in the no-profile-overlap collection may be named only to say\n   the supplied profile cannot implicate them.\n7. Do not infer source files, behavior, ownership, causes, or fixes from\n   unsymbolicated frames.\n8. Several scenarios crossing the threshold in one run are one run-level\n   anomaly, not automatically several independent bugs.\n9. If no pull request overlaps a profiled path, say so and stop. Do not choose a\n   likely culprit.\n10. Describe every proposed action as a hypothesis to validate by rerunning the\n    same profile, never as a confirmed root cause.\n\n## Output\n\nReturn Slack mrkdwn:\n\n- first line:\n  `*AI proposal (profiling evidence only; not a root cause)*`;\n- at most six bullets;\n- one sentence per bullet;\n- pull-request links formatted as `\u003Curl|#number>`;\n- no general disclaimer beyond the required first line.\n\nGood:\n\n> PR #123 changed a file that appears as a hot frame; rerun the same scenario\n> with that change isolated and compare the frame's self time.\n\nNot allowed:\n\n> PR #123 is the cause because its title mentions Perps.\n\nThe title is routing context, not profiling evidence.\n\n## Failure behavior\n\nReturn no proposal when the evidence is missing or malformed. Never fill gaps\nwith repository knowledge or generic optimization advice.\n","# Profiling Regression Proposal\n\nProduce a short, evidence-bound proposal after deterministic profiling tooling\nhas already classified a run. This skill interprets evidence; it does not decide\nwhether a regression exists.\n\n## When To Use\n\nUse this skill only when the caller supplies structured evidence containing:\n\n- findings produced by a deterministic threshold;\n- hot frames extracted from generated CPU-profile reports;\n- recently merged pull requests separated by whether their changed files\n  overlap those hot-frame paths.\n\nDo not use source-tree searches, repository knowledge, issue history, PR titles,\nor general performance heuristics as additional evidence.\n\n## Workflow\n\n1. Treat the supplied evidence object as the only source of truth.\n2. Do not change, second-guess, or reapply the caller's regression threshold.\n3. Mention a file, function, timing, ratio, run, or owner only when it appears\n   in the evidence.\n4. Connect a pull request to a finding only when the caller places it in the\n   profile-overlap collection. A title that mentions the affected feature is\n   not evidence.\n5. A changed file may be discussed only when its path already occurs in a hot\n   frame from the generated profile.\n6. Pull requests in the no-profile-overlap collection may be named only to say\n   the supplied profile cannot implicate them.\n7. Do not infer source files, behavior, ownership, causes, or fixes from\n   unsymbolicated frames.\n8. Several scenarios crossing the threshold in one run are one run-level\n   anomaly, not automatically several independent bugs.\n9. If no pull request overlaps a profiled path, say so and stop. Do not choose a\n   likely culprit.\n10. Describe every proposed action as a hypothesis to validate by rerunning the\n    same profile, never as a confirmed root cause.\n\n## Output\n\nReturn Slack mrkdwn:\n\n- first line:\n  `*AI proposal (profiling evidence only; not a root cause)*`;\n- at most six bullets;\n- one sentence per bullet;\n- pull-request links formatted as `\u003Curl|#number>`;\n- no general disclaimer beyond the required first line.\n\nGood:\n\n> PR #123 changed a file that appears as a hot frame; rerun the same scenario\n> with that change isolated and compare the frame's self time.\n\nNot allowed:\n\n> PR #123 is the cause because its title mentions Perps.\n\nThe title is routing context, not profiling evidence.\n\n## Failure behavior\n\nReturn no proposal when the evidence is missing or malformed. Never fill gaps\nwith repository knowledge or generic optimization advice.\n",{"name":5,"maturity":46,"description":7},"stable","main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill profiling-regression-proposal",{"tool":62,"command":63},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill profiling-regression-proposal",{"tool":65,"command":66},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill profiling-regression-proposal","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal\u002FSKILL.md",true,[70,74,80,84],{"path":71,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":16},"LICENSE","许可证",1065,{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fevidence-schema.md","REFERENCE","参考文档",1354,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal\u002Freferences\u002Fevidence-schema.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"SOURCE.md",384,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal\u002FSOURCE.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-profiling-regression-proposal\u002FTRUST.auto.yaml",[89,116,138,154,167,177],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":41},"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",[],[97,98,99,100,101,102,103,32,104,105,106,107,108,109,110,111,112,113,114,115],"performance","recipe performance","recipe","mm","sentry","harness","app","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":41},"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",[],[125,126,127,128,129,130,131,132,133,134,26,135,136,137],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":41},"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",[],[146,126,147,148,149,150,27,135,26,134,39,151,152,130,153,129,128],"mexc spot rest","REST","admin","signing","Wallet","secure","data","orders",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":120,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":41},"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",[],[162,163,127,164,165,136,26,166,133,132,130,129],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":168,"name":169,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":170,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":41},"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",[],[174,175,176],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":181,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":41},"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",[],[185,186,187,188,189,190,191,38,192,193,194],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]