Security audit
Security checks for vulnerabilities and agentic risk
This skill is only a short Markdown instruction file, but its workflow-automation scope and API-key requirement are too vague for users to understand what access they are granting.
Review this skill carefully before installing. Do not provide a real API key until the publisher documents what service it uses, what data it sends, and supplies the referenced automation script or otherwise explains the execution path.
The skill’s description, 'When to Use' guidance, and usage triggers are so broad that the skill could be invoked for loosely related or unintended tasks. In an agent ecosystem, ambiguous routing increases the chance that automation logic is selected without sufficient user intent validation, which can lead to unintended actions, unsafe workflow execution, or misuse of connected capabilities.
The documentation instructs users to set an API key but gives no warning about where that credential is sent, what external services are contacted, or how transmitted data is handled. This creates risk of inadvertent credential exposure, unsafe secret handling, and unreviewed network/data egress when operators enable the skill.
No suspicious patterns detected.
