[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EN356HW1KKXW0AFGD8A3TM":3,"skill-same:01M7EN356HW1KKXW0AFGD8A3TM":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},"01M7EN356HW1KKXW0AFGD8A3TM","it-asset-management",null,"Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.","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-安全渗透\u002Fit-asset-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: it-asset-management\ndescription: Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.\n---\n\n# IT asset management\n\nThe register exists to answer operational questions: what do we have, who has it, is it supported, is\nit licensed, and when does it need replacing. An inventory that answers none of those is an\naccounting artifact.\n\n## One register, reconciled against reality\n\nA register maintained by hand diverges immediately. Feed it from discovery — what is actually on the\nnetwork and enrolled in management — and reconcile against procurement and finance records.\n\nThe valuable output is the **discrepancy list**: assets in the register that discovery cannot find,\nand devices discovery finds that the register does not know about. The second category is the\nsecurity problem, since an unknown device is unmanaged by definition.\n\n## Ownership, not just location\n\nEvery asset needs a named accountable person. \"The engineering team\" is not an owner; when the device\nneeds patching, returning or replacing, a team does not answer.\n\nTrack state through the lifecycle — ordered, in stock, assigned, in repair, retired, disposed — and\nrequire the state change at the moment of handover. A register updated in batches is a register that\nis wrong between batches, which is most of the time.\n\n## Software licensing\n\nUnder-licensing is a financial and legal exposure that surfaces at audit; over-licensing is money\nspent on nothing, and it is usually the larger number.\n\nReconcile entitlements against actual installs and actual use. Reclaiming licenses from people who\nstopped using a tool typically funds a meaningful fraction of the next renewal, and the data for it\nalready exists.\n\nWatch license models that change cost with infrastructure — per-core, per-socket, per-user in a\nsystem that provisions freely. A routine infrastructure change can multiply a license bill with no\nprocurement decision anywhere in the path.\n\n## Refresh and disposal\n\nPlan refresh on a cycle and budget it as a steady cost through\n`finance:budgeting-and-forecasting`. Refresh driven by failure produces an unpredictable expense and\na worse experience, and it always arrives at the wrong moment.\n\nDisposal is where data escapes. Require certified destruction or verified wipe, keep the certificate,\nand treat storage devices as data until proven otherwise. A drive in a cupboard nobody logged is a\nbreach with no date attached.\n\n## Tooling\n\nDiscovery and hardware inventory: Lansweeper, Snipe-IT, ServiceNow ITAM, Device42, and similar;\nthe endpoint management platform already knows most of the fleet and is the cheapest starting\npoint.\n\nSoftware licensing and SaaS spend: Flexera, Torii, Zylo, Productiv, and similar. The SaaS half is\nwhere the money hides, and it is discovered through the expense system and single sign-on logs as\nmuch as through any inventory tool.\n\nReconcile the register against the endpoint platform, the identity provider and the finance system\non a schedule. Three systems each holding a partial truth is the normal state, and the gaps between\nthem are the assets nobody is managing.\n\n## Never\n\n- Maintain a register by hand and trust it.\n- Record a team as an asset owner.\n- Renew licenses without reconciling against actual use.\n- Dispose of storage without evidence of destruction or wipe.\n","# IT asset management\n\nThe register exists to answer operational questions: what do we have, who has it, is it supported, is\nit licensed, and when does it need replacing. An inventory that answers none of those is an\naccounting artifact.\n\n## One register, reconciled against reality\n\nA register maintained by hand diverges immediately. Feed it from discovery — what is actually on the\nnetwork and enrolled in management — and reconcile against procurement and finance records.\n\nThe valuable output is the **discrepancy list**: assets in the register that discovery cannot find,\nand devices discovery finds that the register does not know about. The second category is the\nsecurity problem, since an unknown device is unmanaged by definition.\n\n## Ownership, not just location\n\nEvery asset needs a named accountable person. \"The engineering team\" is not an owner; when the device\nneeds patching, returning or replacing, a team does not answer.\n\nTrack state through the lifecycle — ordered, in stock, assigned, in repair, retired, disposed — and\nrequire the state change at the moment of handover. A register updated in batches is a register that\nis wrong between batches, which is most of the time.\n\n## Software licensing\n\nUnder-licensing is a financial and legal exposure that surfaces at audit; over-licensing is money\nspent on nothing, and it is usually the larger number.\n\nReconcile entitlements against actual installs and actual use. Reclaiming licenses from people who\nstopped using a tool typically funds a meaningful fraction of the next renewal, and the data for it\nalready exists.\n\nWatch license models that change cost with infrastructure — per-core, per-socket, per-user in a\nsystem that provisions freely. A routine infrastructure change can multiply a license bill with no\nprocurement decision anywhere in the path.\n\n## Refresh and disposal\n\nPlan refresh on a cycle and budget it as a steady cost through\n`finance:budgeting-and-forecasting`. Refresh driven by failure produces an unpredictable expense and\na worse experience, and it always arrives at the wrong moment.\n\nDisposal is where data escapes. Require certified destruction or verified wipe, keep the certificate,\nand treat storage devices as data until proven otherwise. A drive in a cupboard nobody logged is a\nbreach with no date attached.\n\n## Tooling\n\nDiscovery and hardware inventory: Lansweeper, Snipe-IT, ServiceNow ITAM, Device42, and similar;\nthe endpoint management platform already knows most of the fleet and is the cheapest starting\npoint.\n\nSoftware licensing and SaaS spend: Flexera, Torii, Zylo, Productiv, and similar. The SaaS half is\nwhere the money hides, and it is discovered through the expense system and single sign-on logs as\nmuch as through any inventory tool.\n\nReconcile the register against the endpoint platform, the identity provider and the finance system\non a schedule. Three systems each holding a partial truth is the normal state, and the gaps between\nthem are the assets nobody is managing.\n\n## Never\n\n- Maintain a register by hand and trust it.\n- Record a team as an asset owner.\n- Renew licenses without reconciling against actual use.\n- Dispose of storage without evidence of destruction or wipe.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fit-asset-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 it-asset-management",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill it-asset-management",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill it-asset-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fit-asset-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",[],[]]