Warranty Tracking SKILL.md skillA
Warranty Tracking from wyre-ai/msp-claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wyre-ai/msp-claude-plugins/Warranty Tracking@git:20260817.2671d27Pins git:20260817.2671d27 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wyre-ai/msp-claude-plugins
- Path
msp-claude-plugins/assets-pack/skills/warranty-tracking/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260817.2671d27, committed Aug 17, 2026
- First version recorded
- Jul 15, 2026
- Size
- 8,425 bytes
- Repository stars
- 52
- License
- Apache-2.0
Endpoint hardware warranty status across whatever RMM platforms (Datto RMM, NinjaOne, N-central, Kaseya VSA, ConnectWise Automate, Atera, SuperOps, Syncro, Action1, ImmyBot) and documentation tools (IT Glue, Hudu) are connected: the reliability spread between OEM-resolved and hand-entered warranty fields, serial/asset-tag cross-referencing when RMM data is missing or stale, and the expired / expiring-soon / covered / unknown bucketing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Warranty Tracking@sha256:27975b57f5a90d54The line at the top of this page pins the label git:20260817.2671d27, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_rnynfjkypwychmms)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 15, 2026 and Aug 17, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260817.2671d27 latest | 2026-08-17 | 2671d27 | 8,425 B | A | view · diff |
| git:20260804.5567c51 | 2026-08-04 | 5567c51 | 8,426 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 7,864 B | A | view · diff |
| git:20260715.3f05702 | 2026-07-15 | 3f05702 | 8,787 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8425 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
wyre-ai/msp-claude-plugins · 52 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rnynfjkypwychmms GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Warranty Tracking GET https://markdownregistry.com/api/v1/blob/27975b57f5a90d5438c0f39e2f072a28ee59500a3eb41758c1ce268cb34e9d07
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.