pyats-troubleshoot

SUSPICIOUS. The troubleshooting purpose is legitimate and the commands are proportionate, but the skill’s actual execution path depends on unverifiable local MCP scripts that may be third-party and may receive network credentials, device output, and audit content. Risk is driven by opaque intermediary code and undefined data destinations, not by the troubleshooting workflow itself.