T08 · Insecure Dependencies
- Location
SKILL.md:125- Finding
Unpinned and Unnecessary Third-Party Package Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to be a poorly scoped Excel formula helper that asks for command and file access and advertises unrelated automation/API behavior without clear limits.
Install only if you are comfortable reviewing or narrowing the skill first. It should not need shell commands, broad file reads, external APIs, or extra packages for ordinary formula generation; remove exec, restrict file access to user-selected workbooks, and avoid running the pip install commands unless a specific workbook-processing feature requires them in an isolated environment.
SKILL.md:125Unpinned and Unnecessary Third-Party Package Installation
SKILL.md:5Excessive Command-Execution and File-Access Permissions
The description includes an overly broad trigger for translation/localization tasks unrelated to Excel formulas, which can cause the skill to activate in many unintended situations. Because the skill also advertises read/exec capability, overbroad routing materially increases the chance of privileged tools being made available in contexts that do not need them.
Granting or justifying system command execution for an Excel formula generation/diagnosis skill violates least privilege. In this context, exec is not needed for producing formulas or explaining spreadsheet errors, so its presence materially raises the risk of command misuse, environment probing, or unintended local actions if the skill is invoked by an agent.
The manifest description combines Excel-formula functionality with unrelated translation/localization use cases, which misrepresents the skill’s purpose and broadens when agents may invoke it. This kind of scope confusion can cause the skill to be selected in inappropriate contexts, increasing the chance that unnecessary tools like exec/read are exposed during unrelated tasks.
The description states '支持中文交互', presenting a language constraint in the skill's behavior without any opt-in or alternative language choice. Under the language/locale policy, forcing a specific language without user choice is a natural-language policy concern unless clearly justified as region-specific.
Generic activation language such as executing core capabilities with configurable create/query/export actions lacks clear boundaries and encourages use as a general-purpose operator. In a skill with read and exec available, ambiguous invocation wording makes misuse more likely because agents may infer broad authority not actually needed for spreadsheet help.
The skill simultaneously claims no extra API key is needed while its security guidance discusses API-key handling via environment variables. This inconsistency can mislead operators about whether secrets are required, increasing the risk of accidental secret injection, unsafe configuration, or trust in undocumented external dependencies.
The documentation advertises broad file processing, API integration, and command execution capabilities that exceed the stated Excel-formula use case. Overclaiming these capabilities normalizes unnecessary privileged behavior and may prompt an agent to perform filesystem, network, or shell actions unrelated to formula assistance.
Documenting external API/network integration for a formula-focused skill expands its operational scope beyond what users would reasonably expect. This creates unnecessary data exposure risk because spreadsheet content or prompts could be transmitted externally without a strong functional justification.
No suspicious patterns detected.