T08 · Insecure Dependencies
- Location
SKILL.md:57- Finding
Unnecessary and Unpinned Third-Party Dependencies
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a small local content template, calendar, and SEO helper with overstated documentation and unnecessary dependency advice, but no hidden network access, persistence, credential handling, or destructive behavior was found.
Installers should treat this as a local template/calendar helper, not a complete content automation system. Avoid the documented pip install unless the publisher adds real dependencies, and use explicit output paths in a working directory so existing files are not overwritten accidentally.
SKILL.md:57Unnecessary and Unpinned Third-Party Dependencies
The declared description overstates the tool’s functionality. The code is a straightforward command-line helper with three narrow functions: produce platform-specific content scaffolds, generate a basic weekly publishing schedule, and analyze a local file for generic SEO suggestions. Its primary purpose is adjacent to content production, but it falls materially short of an 'entire workflow' automation system and lacks several core declared capabilities such as topic research, true content generation, collaboration, and brand matrix management. There is no suspicious undeclared behavior beyond reading a user-specified file for SEO analysis and optionally writing output files, which is consistent with the implemented commands.
The skill advertises executable script commands and static analysis detected file read/write capabilities, but the manifest declares no permissions or allowed-tools scope. In an agent environment, missing explicit tool scoping can cause the skill to run with broader-than-expected filesystem access, reducing transparency and weakening least-privilege controls.
The trigger keywords are extremely generic ('content creation', 'copywriting') and likely to match many ordinary user requests. Overbroad activation increases the chance the skill is invoked unintentionally, exposing users to unexpected file operations or script execution in contexts where they did not explicitly request this skill.
The module documentation and manifest describe an automated workflow for topic research to content creation, and the CLI advertises commands like 'Generate multi-platform content' and 'Automated Content Creation Tool'. In code, generate_content only returns a framework template with a tip explicitly stating that actual content should be generated separately by an AI model, and there is no topic research implementation anywhere in the file.
The function docstring says 'Generate content for the specified platform and topic', and the CLI help for write says 'Generate content'. However, the returned body ends with a note that it is only a content framework template and that specific content must be generated separately, directly contradicting the documented behavior.
The platform configuration prominently targets WeChat, Zhihu, and Xiaohongshu and encodes platform-specific content styles tied to Chinese-language ecosystems, but the file provides no user-facing opt-in or explanation that the skill is region/language specific. This can amount to a locale-policy issue because the skill implicitly steers output toward a specific locale context without documenting that constraint.
The tool writes directly to a user-supplied output path with Path(args.output).write_text(...) and no overwrite confirmation, safe-write behavior, or path restrictions. In a local automation or agent context, this can unintentionally overwrite existing files, causing data loss or modification of sensitive workspace content if the path is supplied incorrectly or maliciously.
No suspicious patterns detected.