chrome-devtools-cli

The skill presents a coherent capability: automating Chrome DevTools via a CLI to perform browser actions and collect diagnostics. However, the footprint is not fully trustworthy due to unverifiable binaries (chrome-devtools-mcp) and lack of explicit, verifiable install sources. This elevates risk around supply-chain integrity and potential unintended data exposure. The data flows described are primarily local to the browser and user machine, with outputs written to files; no explicit credential handling is evident. Overall, suspicious due to unverifiable binary distribution; classify as SUSPICIOUS with high caution until provenance and install checks are provided.