T01 · Skill Instruction Hijacking
- Location
SKILL.md:127- Finding
Mandatory Third-Party Branding in Generated Research Reports
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This research-report skill is mostly coherent, but it needs review because it installs an unpinned Python package into the system environment and can write reports to an unrestricted output path.
Review this before installing. Use a virtual environment instead of system Python, avoid --break-system-packages, set OUTPUT_FILE only to a safe workspace filename, and check whether you are comfortable with the mandatory branding and the missing DOCX export.
SKILL.md:127Mandatory Third-Party Branding in Generated Research Reports
SKILL.md:45Unpinned Dependency Installation Bypasses System Package Protections
SKILL.md:79Unvalidated Output Path Can Overwrite Files Outside the Intended Directory
The manifest description states that the skill provides '.md and .docx export' as part of its capabilities. However, the implementation only computes a .docx filename variable and the actual workflow saves only OUTFILE_MD, explicitly telling the user to use another skill to convert the markdown to Word format.
The skill instructs the agent to write a file to a user-influenced path (OUTPUT_FILE-derived OUTFILE_MD) without warning about file creation or overwrite behavior. In agent environments with file tools, this can lead to unintended overwriting of existing files or silent creation of files in unexpected locations, especially because the skill frames the write as automatic after report generation.
The setup code defines both markdown and DOCX output filenames, which supports the surrounding documentation's claim of dual-format export. Later, the wrap-up comment and status text state that only the markdown report is saved and that DOCX requires a separate skill, contradicting the apparent intent conveyed earlier in the file.
No suspicious patterns detected.