Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a local China beauty-industry guide, but it quietly ships a structured factory contact list while saying it contains no individual factory contacts.
Review before installing if you are comfortable with a skill that includes named manufacturer records and direct business contact emails despite documenting itself as cluster-level only. There is no evidence of malware, persistence, credential access, or data exfiltration, but the publisher should either remove the contact list or clearly disclose supplier-contact functionality.
The skill is invocable and references implementation in run.py that reads data.json, but the manifest does not declare any tool scope such as permissions or allowed-tools. That creates an authorization/expectation gap: reviewers and runtime policy may not clearly understand that file-read capability is required, which can lead to overbroad defaults or unsafe execution assumptions.
The file exposes a structured directory of direct manufacturer contact email addresses, which goes beyond high-level industry guidance and creates a ready-made target list for unsolicited outreach, spam, phishing, and social-engineering campaigns. Even if some addresses are business contacts, bundling them in a machine-readable dataset increases abuse potential by making harvesting trivial at scale.
The skill’s stated purpose is market guidance on manufacturing clusters and sourcing trends, but it also includes an operational contact directory for specific factories. That mismatch expands the skill from informational analysis into lead generation, making it more useful for abuse such as bulk solicitation, competitor intelligence collection, or targeted phishing against named firms.
The skill is framed exclusively around China and China's beauty manufacturing landscape, but the description does not explicitly state that this geographic focus is an intentional, region-specific scope choice for users selecting the skill. Under the policy rule, locale constraints should either offer user choice or be clearly documented and justified as region-specific.
