playwright-stable-profile

SUSPICIOUS. The overall workflow matches browser automation, but the install instructions are internally inconsistent with the official Playwright CLI package name, and the true behavior depends on unseen local scripts plus a second skill. The capability is plausible for the stated purpose, yet trust is reduced by dependency confusion risk and missing code for the wrappers handling a persistent logged-in profile.

The fragment appears to be a browser-session launcher rather than malware. It contains no evident credential theft, external data exfiltration, or destructive behavior. Remote debugging without authentication and disabling Chromium's sandbox in container mode are significant configuration risks; restrict access to the debugging port and use sandboxing where feasible.