The Change Impact Analysis skill uses Lansweeper inventory data, including OS versions, disk space, installed software, and scan freshness, combined with live external compatibility research to evaluate the risk of a planned software or OS change. It cross-references your environment against vendor system requirements and known issues, then classifies every in-scope asset into a rollout cohort: pilot, Wave 1, holdback, or blocked. The primary output is always a decision: Proceed, Proceed with pilot only, Do not proceed, or Insufficient confidence, with an optional formal Change Impact Analysis document ready for CAB review.

Change management sits at the intersection of two team mandates that rarely talk to each other:
“Are we ready to deploy this?”
Readiness: do assets meet OS, disk, and RAM requirements?
Risk: what software conflicts could break the rollout?
“What happens to our coverage if this goes wrong?”
Agents: will EDR and management tools still work after the change?
Gaps: does this deployment leave any assets unprotected during rollout?
This skill produces a single output both teams can act from.
Lansweeper MCP
https://mcp.lansweeper.com/mcp
Lansweeper plan
Starter, Pro, Enterprise
Traffic Sensor
Optional — required for network- level AI detection (GA end of May 2026)
Claude 3.5+, ChatGPT, Gemini (Antigravity), Copilot
Step 1 — Download
Download the skill package for your platform.
Step 2 — Install
.github/skills/change-impact/SKILL.md for GitHub Copilot.Step 3 — Connect Lansweeper
Web search must also be available on your platform, since the compatibility research step depends on it.
Step 4 — Ask
$change-impact or “we’re upgrading Windows 10 to 11, what’s the risk?”