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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.
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.
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.
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.
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.
Discovery and hardware inventory: Lansweeper, Snipe-IT, ServiceNow ITAM, Device42, and similar; the endpoint management platform already knows most of the fleet and is the cheapest starting point.
Software licensing and SaaS spend: Flexera, Torii, Zylo, Productiv, and similar. The SaaS half is where the money hides, and it is discovered through the expense system and single sign-on logs as much as through any inventory tool.
Reconcile the register against the endpoint platform, the identity provider and the finance system on a schedule. Three systems each holding a partial truth is the normal state, and the gaps between them are the assets nobody is managing.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.