windows-chat-verification

name	windows-chat-verification
description	Verify real Windows chat-app workflows through DesktopManager MCP. Use when an MCP-capable assistant should open a desktop chat app, inspect its window and controls, type into the prompt area, send a message, and verify the visible result with screenshots and structural or app-owned evidence.

Windows Chat Verification

Use this skill when the task is to verify a real Windows chat application through DesktopManager, especially IntelligenceX Chat and similar WebView2 or Chromium-style shells.

Golden Path

1. Make sure the DesktopManager MCP server is available through this plugin.
   • The plugin starts DesktopManager through ./scripts/start-desktopmanager-mcp.ps1.
   • Build DesktopManager.Cli first if the repo has not produced a CLI host yet.
   • Keep the default server read-only unless the verification needs clicks, typing, or layout changes.
2. Enable only the minimum mutation scope you need.
   • Set DESKTOPMANAGER_MCP_ALLOW_MUTATIONS=1 before starting the MCP client session when the workflow needs live interaction.
   • Use DESKTOPMANAGER_MCP_ALLOW_PROCESS=IntelligenceX.Chat.App;DesktopManager.TestApp or another narrow process list when you can.
   • Set DESKTOPMANAGER_MCP_ALLOW_FOREGROUND_INPUT=1 only when a zero-handle UIA editor really needs focused fallback text or key input.
3. Start with inspection, not clicks.
   • Read desktop://windows/visible, desktop://windows/active, and desktop://monitors.
   • Use list_windows, get_active_window, and window_exists before assuming the target app is ready.
   • Capture screenshot_window or when visual proof matters.