Trust Assessment
render-deploy received a trust score of 67/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 2 findings: 1 critical, 0 high, 1 medium, and 0 low severity. Key findings include Unsafe `curl | sh` for CLI installation, API Key exposure in shell commands.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. The LLM Behavioral Safety layer scored lowest at 63/100, indicating areas for improvement.
Last analyzed on February 20, 2026 (commit 458b1186). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings2
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Unsafe `curl | sh` for CLI installation The skill instructs the user to install the Render CLI using `curl -fsSL https://raw.githubusercontent.com/render-oss/cli/main/bin/install.sh | sh`. This method fetches and executes a script directly from a remote URL without any integrity verification (e.g., checksum) or version pinning. If the GitHub repository `render-oss/cli` or the `main` branch is compromised, an attacker could inject malicious code into the `install.sh` script, leading to arbitrary command execution on the user's system with the user's privileges. This constitutes a significant supply chain risk and a direct command injection vector. Recommend using a more secure installation method. For example, provide a checksum for the script and instruct the user to verify it before execution, or suggest installing via a package manager with better integrity checks (like Homebrew, which is already suggested for macOS). Pinning to a specific release tag instead of `main` would also reduce risk. | LLM | SKILL.md:91 | |
| MEDIUM | API Key exposure in shell commands The skill instructs users to configure Render API keys using direct shell commands such as `claude mcp add --header "Authorization: Bearer <YOUR_API_KEY>"`, `export RENDER_API_KEY="<YOUR_API_KEY>"`, and `codex mcp add render --url https://mcp.render.com/mcp --bearer-token-env-var RENDER_API_KEY`. While these are common configuration patterns for CLI tools, passing API keys directly as arguments or setting them as environment variables in the shell can expose them in shell history files (`.bash_history`, `.zsh_history`), process lists (`ps aux`), or system logs. This increases the risk of credential harvesting if the user's system is compromised or if they inadvertently share their screen or shell history. Advise users to use secure credential storage mechanisms (e.g., OS-level secret managers, dedicated credential files with restricted permissions) where available, or to ensure their shell history is not logged for commands containing sensitive information. If the tools support reading secrets from a file or standard input, that would be a more secure alternative. | LLM | SKILL.md:124 |
Scan History
Embed Code
[](https://skillshield.io/report/4b4c648d4bbbbd0b)
Powered by SkillShield