sgdk-input

SUSPICIOUS. The skill’s stated purpose is coherent and the docs are narrowly scoped to SGDK input, but the example workflow tells users to run an unverified third-party Docker image instead of the official SGDK container/build path. No credential harvesting or exfiltration is evident, so this looks more like supply-chain risk than malware.