eoleos-flagging

Solid

Use this skill when identifying devices, operating system versions, or firmware approaching or past end-of-life (EOL) or end-of-support (EOS), combining device inventory data (make/model/OS version) pulled from whatever RMM platforms are connected with general knowledge of common EOL/EOS dates for widely-deployed OS and hardware, and prioritizing the resulting risk list by device criticality. Always use conduit__search_tools to discover which RMM(s) are actually connected before assuming a specific vendor, and always caveat EOL/EOS dates as needing verification against current vendor lifecycle pages since they can change.

AI & Automation 36 stars 16 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 80/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# EOL/EOS Flagging ## Overview End-of-life and end-of-support are two related but distinct events. End-of-life (EOL) generally means the vendor has stopped selling or actively developing the product. End-of-support (EOS) — sometimes called end-of-extended-support — means the vendor stops shipping security patches. EOS is the harder deadline operationally: a device past EOS is accumulating unpatched vulnerabilities with no fix coming, regardless of whether it still "works." This skill flags both, keeps them distinct in the output, and prioritizes the resulting list by how much it actually matters if a given device is left running past its date. This needs two ingredients: **device inventory data** (make, model, OS version, firmware version — pulled live from whatever RMM is connected) and **EOL/EOS knowledge** (which dates apply to which OS/hardware — general knowledge, not something the RMM exposes). The two must be combined explicitly, and the knowledge half must always carry a verification caveat, because vendor lifecycle dates do change (extended support gets purchased, timelines shift) and this skill's knowledge has a cutoff. This is distinct from `warranty-tracking`: a device can be fully in warranty and past OS end-of-support (an aging laptop still under a 5-year warranty but running an OS version no longer patched), or out of warranty and still fully supported (an older desktop on a current, supported OS with no active vendor patching risk). Both signals feed `refr...

Details

Author
wyre-technology
Repository
wyre-technology/msp-claude-plugins
Created
5 months ago
Last Updated
today
Language
Astro
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Solid

refresh-cycle-planning

Use this skill when building a forward-looking hardware refresh calendar by combining warranty expiration, EOL/EOS timing, and device age across whatever RMM platforms and documentation tools are connected through the gateway. Covers how to bucket devices into replace-now, plan-this-year, and monitor tiers so refresh conversations happen proactively — ahead of a failure or a forced EOL migration — rather than reactively after something breaks. Always use conduit__search_tools to discover which tools are actually connected before assuming a specific vendor.

36 Updated today
wyre-technology
Data & Documents Solid

warranty-tracking

Use this skill when pulling and normalizing 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 through the gateway. Covers the reliability spread between RMM warranty fields (some pull directly from OEM APIs, some rely on manually-entered fields that go stale), cross-referencing documentation platforms when RMM warranty data is missing or stale, and flagging devices with expired or soon-expiring warranty. Always use conduit__search_tools to discover which RMM and documentation tools are actually connected before assuming a specific vendor.

36 Updated today
wyre-technology
AI & Automation Featured

feature-flagging

Operational discipline for feature flags as production infrastructure. Flag types, naming, targeting rules, rollout strategy, lifecycle, governance, stale flag management, and the technical debt patterns that bite teams who weren't deliberate about it.

496 Updated 5 days ago
rampstackco