[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GYTFVSW7SCAQ2BNMAKW9GP":3,"skill-same:01M6GYTFVSW7SCAQ2BNMAKW9GP":83},{"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":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6GYTFVSW7SCAQ2BNMAKW9GP","hand-off-incident-command-at-shift-change",null,"Use when the current incident commander is going off-shift. Runs a structured handoff of roles, state, open hypotheses, and in-flight tasks, with a zero-tolerance rule against blaming the outgoing commander.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",80,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-hand-off-incident-command-at-shift-change\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-hand-off-incident-command-at-shift-change\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"change","hand off incident command at shift change","at","hand","incident","command","open","incident commander","use","structured handoff","ZeRO","structured","roles","commander","rule","with","tolerance","state","tasks","handoff","when","2026-11-10 10:12:30",false,"---\nname: hand-off-incident-command-at-shift-change\ndescription: Use when the current incident commander is going off-shift. Runs a structured handoff of roles, state, open hypotheses, and in-flight tasks, with a zero-tolerance rule against blaming the outgoing commander.\n---\n\n# Hand Off Incident Command at Shift Change\n\nAn incident spanning a shift boundary dies at the seam unless command transfers with the rigour of a surgery handover: state, open questions, and what has already been ruled out. Blamelessness here means the incoming IC inherits the situation, not a defence of it.\n\n## Procedure\n\n1. Freeze the outgoing IC's decision log and publish a handoff block in the incident channel:\n\n       HANDOFF 22:00Z IC: @ana -> @ben\n       State: mitigated, error rate 0.4%, cause still open.\n       Open hypotheses: (1) pool leak in 4.18 (2) upstream 503s. Ruled out: DB CPU, network.\n       In flight: heap dump uploading; vendor ticket 8842.\n       Next update due 22:15. Do NOT restart the pool until the dump finishes.\n\n2. Walk the incoming IC through the last three decision-log entries verbatim, not a paraphrase.\n3. Transfer the pinned runbook, the comms cadence timer, and the escalation contacts.\n4. The incoming IC restates the state and next action in their own words; if the restatement is wrong, the handoff is not done.\n5. Keep the outgoing IC reachable for one cadence interval, then explicitly release them: \"you're off, @ben owns it.\"\n6. If the outgoing IC made an error, log it as a fact in the timeline — never as an accusation in the handoff.\n7. Confirm the incoming IC knows who their deputy is and when their own shift ends.\n8. State which of the three bridge roles (IC, comms, scribe) also change hands, not just the IC.\n\n## Pitfalls\n\n- Handing off \"it's mostly under control\" with no state line, so the incoming IC re-investigates ruled-out ground.\n- The outgoing IC stays on the call and keeps deciding, producing two commanders and contradictory fixes.\n- Losing the in-flight task list, so a heap dump or vendor ticket is forgotten at the seam.\n- Blaming the outgoing shift for a mitigation that looks wrong in hindsight, which teaches everyone to hide state.\n- Handing off the IC role but silently keeping the comms role, so two people post conflicting updates.\n- Restating hypotheses as facts during handoff, re-infecting the new shift with a guess the old one had already doubted.\n\n## Verification\n\n```\n    grep -A6 'HANDOFF ' incident\u002FSEV*-2026-*.md | tail\n    # passes when state, open hypotheses, in-flight tasks, and a due time all appear and the incoming IC restated them\n```\n\nRelated: the incoming IC reads `keep-an-incident-decision-log` entries verbatim, not a summary.\n","# Hand Off Incident Command at Shift Change\n\nAn incident spanning a shift boundary dies at the seam unless command transfers with the rigour of a surgery handover: state, open questions, and what has already been ruled out. Blamelessness here means the incoming IC inherits the situation, not a defence of it.\n\n## Procedure\n\n1. Freeze the outgoing IC's decision log and publish a handoff block in the incident channel:\n\n       HANDOFF 22:00Z IC: @ana -> @ben\n       State: mitigated, error rate 0.4%, cause still open.\n       Open hypotheses: (1) pool leak in 4.18 (2) upstream 503s. Ruled out: DB CPU, network.\n       In flight: heap dump uploading; vendor ticket 8842.\n       Next update due 22:15. Do NOT restart the pool until the dump finishes.\n\n2. Walk the incoming IC through the last three decision-log entries verbatim, not a paraphrase.\n3. Transfer the pinned runbook, the comms cadence timer, and the escalation contacts.\n4. The incoming IC restates the state and next action in their own words; if the restatement is wrong, the handoff is not done.\n5. Keep the outgoing IC reachable for one cadence interval, then explicitly release them: \"you're off, @ben owns it.\"\n6. If the outgoing IC made an error, log it as a fact in the timeline — never as an accusation in the handoff.\n7. Confirm the incoming IC knows who their deputy is and when their own shift ends.\n8. State which of the three bridge roles (IC, comms, scribe) also change hands, not just the IC.\n\n## Pitfalls\n\n- Handing off \"it's mostly under control\" with no state line, so the incoming IC re-investigates ruled-out ground.\n- The outgoing IC stays on the call and keeps deciding, producing two commanders and contradictory fixes.\n- Losing the in-flight task list, so a heap dump or vendor ticket is forgotten at the seam.\n- Blaming the outgoing shift for a mitigation that looks wrong in hindsight, which teaches everyone to hide state.\n- Handing off the IC role but silently keeping the comms role, so two people post conflicting updates.\n- Restating hypotheses as facts during handoff, re-infecting the new shift with a guess the old one had already doubted.\n\n## Verification\n\n```\n    grep -A6 'HANDOFF ' incident\u002FSEV*-2026-*.md | tail\n    # passes when state, open hypotheses, in-flight tasks, and a due time all appear and the incoming IC restated them\n```\n\nRelated: the incoming IC reads `keep-an-incident-decision-log` entries verbatim, not a summary.\n",{"name":5,"description":7},"main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fpayments\u002F0xklen-hand-off-incident-command-at-shift-change",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-11 08:47:40",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill hand-off-incident-command-at-shift-change",{"tool":61,"command":62},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill hand-off-incident-command-at-shift-change",{"tool":64,"command":65},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill hand-off-incident-command-at-shift-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-hand-off-incident-command-at-shift-change\u002FSKILL.md",true,[69,73,79],{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",1063,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"SOURCE.md","REFERENCE","参考文档",367,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-hand-off-incident-command-at-shift-change\u002FSOURCE.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-hand-off-incident-command-at-shift-change\u002FTRUST.auto.yaml",[84,111,134,152,165,175],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[92,93,94,95,96,97,98,99,100,101,102,103,104,38,105,106,107,108,109,110],"performance","recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","react","browser","layout","screen","network","metamask",{"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":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",[],[120,121,122,123,124,125,126,127,128,129,130,131,132,133],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","for","api keys","maintenance","protobuf",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"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",[],[142,121,143,144,145,146,147,131,130,129,148,149,150,125,151,124,123],"mexc spot rest","REST","admin","signing","Wallet","requests","actions","secure","data","orders",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":115,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"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",[],[160,161,122,162,163,132,130,164,128,127,125,124],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":166,"name":167,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":171,"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",[],[172,173,174],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":182,"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",[],[183,184,185,186,187,188,189,28,190,191,192],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]