[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMXEZFMHTJVYEC6VN8BVC6":3,"skill-same:01M7EMXEZFMHTJVYEC6VN8BVC6":46},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EMXEZFMHTJVYEC6VN8BVC6","incident-management",null,"Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes. Use this to set up an incident process, run one, work out why the same failure keeps recurring, or fix a review practice that generates findings nobody closes.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fincident-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: incident-management\ndescription: Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes. Use this to set up an incident process, run one, work out why the same failure keeps recurring, or fix a review practice that generates findings nobody closes.\n---\n\n# Incident management\n\nAn incident is any unplanned disruption significant enough that normal work stops until it is\nresolved. The discipline exists because the instincts that serve people well in ordinary work —\ninvestigate thoroughly, decide carefully, keep everyone informed — all fail under time pressure\nunless someone has structured them in advance.\n\nThis covers operational incidents generally. For security incidents, where evidence preservation\nand disclosure obligations change the order of operations, see `security:incident-response`.\n\n## Declare it, and say so out loud\n\nThe most expensive minutes are the ones spent deciding whether this is an incident. Set a low\nthreshold for declaring and accept that some declarations will be withdrawn — an incident stood\ndown after twenty minutes costs far less than one that ran for two hours as a conversation between\nthree people who each assumed someone else had it.\n\nSeverity should be defined in advance, in terms of customer impact rather than internal\ninconvenience, with each level carrying a stated response: who is notified, how fast, and who can\nbe woken.\n\n## Name a commander who does not fix anything\n\nOne person owns the incident: they decide, they sequence, they assign. **They should not be the\nperson with their hands in the system** — the moment the commander starts debugging, nobody is\nrunning the incident and the timeline stops being kept.\n\nSeparate three roles even in a small response: the commander, the people restoring service, and\none person handling communication. Combining the first and third is survivable; combining the\nfirst and second is how incidents run long without anyone noticing they have.\n\n## Restore first, understand later\n\nThe goal during the incident is service restored, not cause understood. Roll back, fail over,\ndisable the feature, add capacity — whatever returns the customer to working. Diagnosis is\ntomorrow's work, and pursuing it while people are affected is the most common way a thirty-minute\noutage becomes a four-hour one.\n\n**Preserve what you will need to diagnose before you destroy it.** Capture logs, a snapshot, the\ncurrent state — then restore. This is the one step where a minute spent now saves the entire\nreview.\n\n## Keep a timeline while it is happening\n\nWritten as it happens, not reconstructed afterward. What was observed, what was changed, at what\ntime, by whom. Memory of an incident is unreliable within hours and the timeline is what makes the\nreview worth anything.\n\nOne channel, and everything in it. Side conversations produce a response where two people are\nacting on different information.\n\n## Communicate on a rhythm, including when there is nothing new\n\nSay what is happening, what you are doing, what the impact is, and when you will next update — then\nsend that next update on time even if it says nothing has changed. Silence is read as absence, and\nthe update cost is trivial compared to the calls it prevents.\n\nDo not speculate on cause while the incident is open. An early theory shared externally and later\nwithdrawn does more damage than the outage.\n\n## Declare it over deliberately\n\nService restored is not the same as incident closed. Confirm recovery is holding, confirm the\nbacklog it created has been worked through, and say explicitly that it is over so people can stop.\n\n## Run the review on the system, not the person\n\nWithin a few days, while memory is fresh. The question is what about the system made this failure\npossible and made it take this long to resolve — not who typed the command. A review that produces\nblame produces less information every subsequent time, because people stop volunteering what\nactually happened.\n\n**Produce one or two changes, not fifteen.** A short list that gets done beats a thorough list that\ndoes not, and an unclosed action from a previous incident is the most common finding in the next\none. Track them to completion somewhere visible, with owners and dates.\n\n## Never\n\n- Debug while nobody is commanding.\n- Destroy the state you will need to diagnose in order to restore a minute sooner.\n- Skip a scheduled update because there is nothing new to say.\n- Close a review with more actions than the organization will actually complete.\n","# Incident management\n\nAn incident is any unplanned disruption significant enough that normal work stops until it is\nresolved. The discipline exists because the instincts that serve people well in ordinary work —\ninvestigate thoroughly, decide carefully, keep everyone informed — all fail under time pressure\nunless someone has structured them in advance.\n\nThis covers operational incidents generally. For security incidents, where evidence preservation\nand disclosure obligations change the order of operations, see `security:incident-response`.\n\n## Declare it, and say so out loud\n\nThe most expensive minutes are the ones spent deciding whether this is an incident. Set a low\nthreshold for declaring and accept that some declarations will be withdrawn — an incident stood\ndown after twenty minutes costs far less than one that ran for two hours as a conversation between\nthree people who each assumed someone else had it.\n\nSeverity should be defined in advance, in terms of customer impact rather than internal\ninconvenience, with each level carrying a stated response: who is notified, how fast, and who can\nbe woken.\n\n## Name a commander who does not fix anything\n\nOne person owns the incident: they decide, they sequence, they assign. **They should not be the\nperson with their hands in the system** — the moment the commander starts debugging, nobody is\nrunning the incident and the timeline stops being kept.\n\nSeparate three roles even in a small response: the commander, the people restoring service, and\none person handling communication. Combining the first and third is survivable; combining the\nfirst and second is how incidents run long without anyone noticing they have.\n\n## Restore first, understand later\n\nThe goal during the incident is service restored, not cause understood. Roll back, fail over,\ndisable the feature, add capacity — whatever returns the customer to working. Diagnosis is\ntomorrow's work, and pursuing it while people are affected is the most common way a thirty-minute\noutage becomes a four-hour one.\n\n**Preserve what you will need to diagnose before you destroy it.** Capture logs, a snapshot, the\ncurrent state — then restore. This is the one step where a minute spent now saves the entire\nreview.\n\n## Keep a timeline while it is happening\n\nWritten as it happens, not reconstructed afterward. What was observed, what was changed, at what\ntime, by whom. Memory of an incident is unreliable within hours and the timeline is what makes the\nreview worth anything.\n\nOne channel, and everything in it. Side conversations produce a response where two people are\nacting on different information.\n\n## Communicate on a rhythm, including when there is nothing new\n\nSay what is happening, what you are doing, what the impact is, and when you will next update — then\nsend that next update on time even if it says nothing has changed. Silence is read as absence, and\nthe update cost is trivial compared to the calls it prevents.\n\nDo not speculate on cause while the incident is open. An early theory shared externally and later\nwithdrawn does more damage than the outage.\n\n## Declare it over deliberately\n\nService restored is not the same as incident closed. Confirm recovery is holding, confirm the\nbacklog it created has been worked through, and say explicitly that it is over so people can stop.\n\n## Run the review on the system, not the person\n\nWithin a few days, while memory is fresh. The question is what about the system made this failure\npossible and made it take this long to resolve — not who typed the command. A review that produces\nblame produces less information every subsequent time, because people stop volunteering what\nactually happened.\n\n**Produce one or two changes, not fifteen.** A short list that gets done beats a thorough list that\ndoes not, and an unclosed action from a previous incident is the most common finding in the next\none. Track them to completion somewhere visible, with owners and dates.\n\n## Never\n\n- Debug while nobody is commanding.\n- Destroy the state you will need to diagnose in order to restore a minute sooner.\n- Skip a scheduled update because there is nothing new to say.\n- Close a review with more actions than the organization will actually complete.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fincident-management",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill incident-management",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill incident-management",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill incident-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fincident-management\u002FSKILL.md",true,[],[47,55,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":54},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":56,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":54},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":54},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":54},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":54},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":54},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]