content-engine

SUSPICIOUS: The core browser-orchestration purpose is coherent, but the install trust is not. The skill depends on a third-party browser automation CLI with a publisher mismatch in the instructions, then uses it to manage persistent authenticated sessions for multiple external services. No clear malicious exfiltration is shown, but the provenance inconsistency plus credential-like session handling make the skill medium/high risk.

SUSPICIOUS due to compounded trust and semi-autonomous distribution, but not malicious. The core capabilities fit a content-generation studio, and the main installer/data flows point to official same-org or named provider endpoints; the biggest risks are curl|sh install hygiene, saved browser sessions, and transitive invocation of other skills that may publish or act downstream.