Trust Assessment
hetzner-provisioner received a trust score of 88/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 1 finding: 0 critical, 1 high, 0 medium, and 0 low severity. Key findings include Potential Command Injection via API Token Storage.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 14, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings1
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| HIGH | Potential Command Injection via API Token Storage The skill describes a process for handling the `HETZNER_API_TOKEN`. It includes a regex validation step (`[[ ! "$HETZNER_API_TOKEN" =~ ^[a-zA-Z0-9]{64}$ ]]`) to check if the token is 64 alphanumeric characters. However, if the validation fails, the skill prompts the user with 'Continue anyway? (yes/no)'. If the user provides a token containing shell metacharacters (e.g., `invalid_token; malicious_command; #`) and chooses to continue, the skill will proceed to save this unsanitized input directly into the `.env` file using `echo "HETZNER_API_TOKEN=$HETZNER_API_TOKEN" >> .env`. If this `.env` file is later sourced by another process or the user, or if the variable's content is used in an unquoted shell context, the embedded malicious command could be executed, leading to arbitrary command injection. 1. **Enforce strict validation**: Do not allow the user to 'Continue anyway?' if the token format is invalid. The skill should strictly require a 64-alphanumeric character token. 2. **Sanitize input**: If there's a legitimate reason to store non-standard tokens, ensure that any user-provided input is properly escaped or quoted before being written to a file or used in a shell command. 3. **Use safer methods**: Instead of direct `echo` with user input, consider using a library function that safely writes environment variables to a file, or explicitly quote the variable in the `.env` file (e.g., `HETZNER_API_TOKEN="$HETZNER_API_TOKEN"`). | LLM | SKILL.md:74 |
Scan History
Embed Code
[](https://skillshield.io/report/d3d9c6f4cf1fb8a5)
Powered by SkillShield