add-slack

The skill's stated purpose (Slack channel integration and setup) is plausible, but the actual footprint raises security concerns. It relies on pulling and merging code from an external repository (transitive installation), collects and stores Slack tokens, and forwards those credentials to a third-party codepath. These patterns create credential exposure risk and supply-chain risk beyond what is typical for a self-contained integration. While not conclusively malicious, the combination of external code, credential handling, and environment persistence warrants a suspicious risk posture and requires strict controls: code provenance verification, pinned dependencies, secrets-management practices, and explicit per-action user approvals for external code integration.