Change Impact Analysis

Assess the risk of deploying, upgrading, or removing software across your Lansweeper environment — and get a clear Proceed, Pilot, or Hold recommendation before you touch anything.

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.

Why Change Impact Matters Here

Change management sits at the intersection of two team mandates that rarely talk to each other:

  • IT perspective

    “Are we ready to deploy this?”
    Readiness: do assets meet OS, disk, and RAM requirements?
    Risk: what software conflicts could break the rollout?

  • Security perspective

    “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.

Requirements

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)

LLM

Claude 3.5+, ChatGPT, Gemini (Antigravity), Copilot

Step by step setup guide

Step 1 — Download
Download the skill package for your platform.

Step 2 — Install

  • Claude: install as a plugin/skill in Claude Desktop or Code.
  • ChatGPT: install as an app (Developer Mode / Apps SDK).
  • Gemini (Antigravity): load its SKILL.md and bundled files into your agent’s skill folder.
  • Copilot: import as a solution in Copilot Studio, or place at .github/skills/change-impact/SKILL.md for GitHub Copilot.

Step 3 — Connect Lansweeper

  • Claude: connect the Lansweeper MCP connector and sign in. Required — the skill will not run without it.
  • ChatGPT: connect Lansweeper MCP — EU or US endpoint per your tenant.
  • Gemini (Antigravity): connect a Lansweeper MCP connector separately.
  • Copilot: open the agent and connect the Lansweeper MCP connector under its Tools.

Web search must also be available on your platform, since the compatibility research step depends on it.

Step 4 — Ask

  • Claude: “What’s the impact of deploying CrowdStrike to all servers?” or “can we upgrade SQL Server from 2017 to 2022?”
  • ChatGPT: trigger with $change-impact or “we’re upgrading Windows 10 to 11, what’s the risk?”
  • Gemini (Antigravity): “What would break if we remove Java 8?”
  • Copilot: “CAB report for the CrowdStrike rollout.”