setup-coolify-devops

SUSPICIOUS. The skill’s infrastructure-management capabilities largely fit its stated purpose, and storing tokens outside the repo is sensible. The main concern is install/execution trust and data-flow integrity: it requires a third-party MCP package (`@masonator/coolify-mcp@latest`) and forwards a privileged Coolify token to it, plus uses transitive skill installation and root SSH. That is coherent for DevOps automation but higher-risk than a benign documentation-only skill, especially because the MCP component is third-party and unpinned.

The configuration itself does not demonstrate malware, but it creates a supply-chain and credential-exposure risk by automatically executing the unpinned @masonator/coolify-mcp@latest npm package and providing it with a Coolify access token. Pin a reviewed package version or integrity hash, review the package source and permissions, and use a narrowly scoped token.