warranty-trackinglisted

# Warranty Tracking ## Overview Warranty status is the single-most load-bearing field in hardware asset management and the least consistently reliable one across RMM platforms. Some RMMs resolve warranty directly from the OEM (serial-number lookup against Dell/HP/Lenovo warranty APIs) and refresh it automatically. Others expose a warranty field that is purely a manually-entered value someone typed in once during onboarding and never touched again. Treating both as equally trustworthy produces confident-sounding reports built on stale data. This skill covers how to pull warranty data across whatever RMM(s) an org has connected, how to weigh its reliability, and how to fall back to documentation platforms (IT Glue, Hudu) when RMM data is missing or looks stale. This is endpoint/hardware warranty specifically — physical device coverage status. It is not network/cloud infrastructure health (see `cloudops-pack`) and it is not a service-desk ticket about a broken device (see `ops-pack`); a device can be fully healthy and in active use while still being three weeks from warranty expiration, which is exactly the case this skill exists to catch before it becomes a support problem. ## Anti-triggers - **One platform's own warranty or lifecycle field** — "what does Auvik return for warranty," "read N-central's lifecycle record" is that connector's API surface; use `auvik-devices` or `ncentral-devices`. - **ScalePad Lifecycle Manager's warranty product** — LM holds its own hard