it-asset-management
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.
git clone --depth 1 https://github.com/cbrock84/headcount /tmp/it-asset-management && cp -r /tmp/it-asset-management/plugins/it-operations/skills/it-asset-management ~/.claude/skills/it-asset-managementSKILL.md
# IT asset management The register exists to answer operational questions: what do we have, who has it, is it supported, is it licensed, and when does it need replacing. An inventory that answers none of those is an accounting artifact. ## One register, reconciled against reality A register maintained by hand diverges immediately. Feed it from discovery — what is actually on the network and enrolled in management — and reconcile against procurement and finance records. The valuable output is the **discrepancy list**: assets in the register that discovery cannot find, and devices discovery finds that the register does not know about. The second category is the security problem, since an unknown device is unmanaged by definition. ## Ownership, not just location Every asset needs a named accountable person. "The engineering team" is not an owner; when the device needs patching, returning or replacing, a team does not answer. Track state through the lifecycle — ordered, in stock, assigned, in repair, retired, disposed — and require the state change at the moment of handover. A register updated in batches is a register that is wrong between batches, which is most of the time. ## Software licensing Under-licensing is a financial and legal exposure that surfaces at audit; over-licensing is money spent on nothing, and it is usually the larger number. Reconcile entitlements against actual installs and actual use. Reclaiming licenses from people who stopped using a tool typically funds a meaningful fraction of the next renewal, and the data for it already exists. Watch license models that change cost with infrastructure — per-core, per-socket, per-user in a system that provisions freely. A routine infrastructure change can multiply a license bill with no procurement decision anywhere in the path. ## Refresh and disposal Plan refresh on a cycle and budget it as a steady cost through `finance:budgeting-and-forecasting`. Refresh driven by failure produces an unpredictable expense and a worse experience, and it always arrives at the wrong moment. Disposal is where data escapes. Require certified destruction or verified wipe, keep the certificate, and treat storage devices as data until proven otherwise. A drive in a cupboard nobody logged is a breach with no date attached. ## Never - Maintain a register by hand and trust it. - Record a team as an asset owner. - Renew licenses without reconciling against actual use. - Dispose of storage without evidence of destruction or wipe.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.
Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.