Trust Assessment
clawdbot-release-check received a trust score of 73/100, placing it in the Caution category. This skill has some security considerations that users should review before deployment.
SkillShield's automated analysis identified 4 findings: 0 critical, 0 high, 4 medium, and 0 low severity. Key findings include Sensitive environment variable access: $HOME, Insecure temporary file creation in check.sh, Insecure temporary file creation in setup.sh.
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 October 1, 2026 (commit 439cd3a9). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings4
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Sensitive environment variable access: $HOME Access to sensitive environment variable '$HOME' detected in shell context. Verify this environment variable access is necessary and the value is not exfiltrated. | Static | clawdbot/clawdbot-release-check/scripts/check.sh:7 | |
| MEDIUM | Sensitive environment variable access: $HOME Access to sensitive environment variable '$HOME' detected in shell context. Verify this environment variable access is necessary and the value is not exfiltrated. | Static | clawdbot/clawdbot-release-check/scripts/setup.sh:43 | |
| MEDIUM | Insecure temporary file creation in check.sh The script writes to a hardcoded temporary file path '/tmp/cache-update.json' in the shared '/tmp' directory. A local attacker could exploit this by creating a symlink at this path pointing to a sensitive file owned by the victim, leading to arbitrary file overwrite when the script is executed. Use 'mktemp' to generate a secure, unique temporary file path instead of a hardcoded one, e.g., 'tmpfile=$(mktemp)'. Ensure the temporary file is cleaned up on exit. | LLM | scripts/check.sh:136 | |
| MEDIUM | Insecure temporary file creation in setup.sh The script writes to a hardcoded temporary file path '/tmp/cron-updated.json' in the shared '/tmp' directory. A local attacker could exploit this by creating a symlink at this path pointing to a sensitive file owned by the victim, leading to arbitrary file overwrite when the script is executed. Use 'mktemp' to generate a secure, unique temporary file path instead of a hardcoded one, e.g., 'tmpfile=$(mktemp)'. Ensure the temporary file is cleaned up on exit. | LLM | scripts/setup.sh:47 |
Scan History
Embed Code
[](https://skillshield.io/report/9fa229e7b141e8c2)
Powered by SkillShield