[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETCZABFZNN8MZRAZH2KPP4":3,"skill-same:01M7ETCZABFZNN8MZRAZH2KPP4":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},"01M7ETCZABFZNN8MZRAZH2KPP4","systems-administration",null,"Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.","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-安全渗透\u002Fsystems-administration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: systems-administration\ndescription: Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.\n---\n\n# Systems administration\n\nWell-run systems are boring. The work is in the routine that keeps them that way, and almost every\nserious incident traces back to a routine that was skipped.\n\nCloud environment design belongs to `technology:cloud-infrastructure`; this is operating the systems\nthe company runs on.\n\n## Configuration baselines and drift\n\nEvery system class needs a defined baseline: build, hardening, agents, logging, accounts. Systems\nbuilt by hand from memory diverge immediately and cannot be reasoned about as a group.\n\nDrift is the real enemy. Detect it continuously and correct rather than document — a system that no\nlonger matches its baseline is a system whose behavior under patching or failover is unknown.\n\nThe strongest form is disposability: rebuild rather than repair. A system you can rebuild in an hour\nnever accumulates the sediment of a decade of manual fixes.\n\n## Patching as a cadence\n\nSet a regular, predictable window and hold it. Ad hoc patching means patching happens when someone\nworries, which is never in proportion to actual risk.\n\nTier by exposure: internet-facing systems on the shortest cycle, then internal, then isolated.\nEmergency patching is a separate path with its own authority, used for actively exploited\nvulnerabilities — `security:vulnerability-management` decides what is urgent, this skill executes it.\n\nTrack **coverage**, not activity. \"Patching is running\" is not an answer; \"97% of servers are within\n30 days, here are the twelve that are not and why\" is.\n\n## Change control proportionate to risk\n\nHeavyweight approval for trivial changes produces circumvention, and circumvention produces\nunrecorded changes, which is worse than no process.\n\nTier it: standard pre-approved changes, normal changes with review, emergency changes with\nafter-the-fact record. Every change needs an owner, a back-out plan, and a record — the back-out plan\nbeing the part most often assumed rather than written.\n\nMaintenance windows exist to make disruption predictable. Announce them, keep them, and finish inside\nthem.\n\n## Know what you have\n\nAn unmanaged system is a system nobody patches. Reconcile what is running against\n`it-operations:it-asset-management` regularly, and treat anything unaccounted for as urgent — the\nserver nobody owns is the one still running an unsupported operating system.\n\n## Never\n\n- Repair a drifted system without correcting the baseline that let it drift.\n- Patch on worry rather than cadence.\n- Make a change with no back-out plan.\n- Leave a discovered unmanaged system unclaimed.\n","# Systems administration\n\nWell-run systems are boring. The work is in the routine that keeps them that way, and almost every\nserious incident traces back to a routine that was skipped.\n\nCloud environment design belongs to `technology:cloud-infrastructure`; this is operating the systems\nthe company runs on.\n\n## Configuration baselines and drift\n\nEvery system class needs a defined baseline: build, hardening, agents, logging, accounts. Systems\nbuilt by hand from memory diverge immediately and cannot be reasoned about as a group.\n\nDrift is the real enemy. Detect it continuously and correct rather than document — a system that no\nlonger matches its baseline is a system whose behavior under patching or failover is unknown.\n\nThe strongest form is disposability: rebuild rather than repair. A system you can rebuild in an hour\nnever accumulates the sediment of a decade of manual fixes.\n\n## Patching as a cadence\n\nSet a regular, predictable window and hold it. Ad hoc patching means patching happens when someone\nworries, which is never in proportion to actual risk.\n\nTier by exposure: internet-facing systems on the shortest cycle, then internal, then isolated.\nEmergency patching is a separate path with its own authority, used for actively exploited\nvulnerabilities — `security:vulnerability-management` decides what is urgent, this skill executes it.\n\nTrack **coverage**, not activity. \"Patching is running\" is not an answer; \"97% of servers are within\n30 days, here are the twelve that are not and why\" is.\n\n## Change control proportionate to risk\n\nHeavyweight approval for trivial changes produces circumvention, and circumvention produces\nunrecorded changes, which is worse than no process.\n\nTier it: standard pre-approved changes, normal changes with review, emergency changes with\nafter-the-fact record. Every change needs an owner, a back-out plan, and a record — the back-out plan\nbeing the part most often assumed rather than written.\n\nMaintenance windows exist to make disruption predictable. Announce them, keep them, and finish inside\nthem.\n\n## Know what you have\n\nAn unmanaged system is a system nobody patches. Reconcile what is running against\n`it-operations:it-asset-management` regularly, and treat anything unaccounted for as urgent — the\nserver nobody owns is the one still running an unsupported operating system.\n\n## Never\n\n- Repair a drifted system without correcting the baseline that let it drift.\n- Patch on worry rather than cadence.\n- Make a change with no back-out plan.\n- Leave a discovered unmanaged system unclaimed.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fsystems-administration",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 systems-administration",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill systems-administration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill systems-administration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsystems-administration\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",[],[]]