Trust Assessment
redis-gen received a trust score of 62/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 3 findings: 1 critical, 0 high, 1 medium, and 1 low severity. Key findings include Unpinned npm dependency version, Direct User Input to LLM Prompt, Unpinned Dependencies in package.json.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. The LLM Behavioral Safety layer scored lowest at 68/100, indicating areas for improvement.
Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Direct User Input to LLM Prompt The skill directly passes user-provided input (the `<description>` argument from the command line) as the `user` message content to the OpenAI API. This allows an attacker to perform prompt injection, potentially overriding the system prompt, extracting sensitive information from the LLM, or manipulating its output to generate undesirable content. Implement robust input sanitization and validation for the user's description. Consider using a prompt engineering framework that separates user input from system instructions, or employ a less powerful LLM to rephrase/validate user input before passing it to the main generation model. Ensure the system prompt is sufficiently robust to resist common injection techniques. | LLM | src/index.ts:9 | |
| MEDIUM | Unpinned npm dependency version Dependency 'commander' is not pinned to an exact version ('^12.1.0'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/lxgicstudios/redis-gen/package.json | |
| LOW | Unpinned Dependencies in package.json The `package.json` file specifies dependencies using caret (`^`) ranges (e.g., `commander: "^12.1.0"`). While `package-lock.json` pins exact versions for deterministic builds, a fresh `npm install` without a lockfile, or if the lockfile is ignored, could pull in newer minor or patch versions. This introduces a supply chain risk if a future version of a dependency contains a vulnerability or breaking change that is automatically introduced into the build. Pin exact versions for all dependencies in `package.json` (e.g., `"commander": "12.1.0"`) to ensure consistent and predictable builds across all environments. Regularly audit dependencies for known vulnerabilities and update them deliberately. | LLM | package.json:10 |
Scan History
Embed Code
[](https://skillshield.io/report/9f94c369d43e7492)
Powered by SkillShield