Security Audit
common-installation-troubleshooting
github.com/openclaw/skillsTrust Assessment
common-installation-troubleshooting received a trust score of 79/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 4 findings: 0 critical, 0 high, 3 medium, and 1 low severity. Key findings include Missing required field: name, Recommendation to use `npm install --force` flag, Recommendation of specific `npm` packages introduces supply chain risk.
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 Findings4
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Missing required field: name The 'name' field is required for claude_code skills but is missing from frontmatter. Add a 'name' field to the SKILL.md frontmatter. | Static | skills/dawai2005/common-installation-troubleshooting/SKILL.md:1 | |
| MEDIUM | Recommendation to use `npm install --force` flag The skill recommends using `npm install -g clawhub --force` to resolve installation issues. The `--force` flag bypasses peer dependency checks and can overwrite existing files, which can lead to an unstable environment or, in the context of a malicious package, facilitate unauthorized file modification or persistence. This lowers the security posture by disabling built-in safety mechanisms. Advise against using `--force` unless absolutely necessary and with a full understanding of its implications. Suggest alternative troubleshooting steps or more targeted fixes that do not bypass safety checks. If a package requires `--force`, investigate why. | LLM | SKILL.md:59 | |
| MEDIUM | Recommendation of specific `npm` packages introduces supply chain risk The skill advises installing specific `npm` packages such as `tavily-mcp` and `clawhub`. While these packages may be legitimate, any recommendation to install third-party software from a public registry introduces a supply chain risk. If these packages were to be compromised (e.g., through maintainer account takeover, malicious dependency injection, or typosquatting), following these instructions would lead to the installation of malicious software. The skill also corrects a package name from `tavily-search` to `tavily-mcp`, highlighting the potential for typosquatting. Emphasize verifying package authenticity and integrity (e.g., checking checksums, reviewing source code, using private registries) before installation. Advise users to be cautious about installing packages from untrusted sources and to always verify package names and maintainers. | LLM | SKILL.md:20 | |
| LOW | Recommendation to use `npm run` command The skill suggests using `npm run -g clawhub -- --help` to verify installation. The `npm run` command executes scripts defined in a package's `package.json`. If the `clawhub` package were compromised, or if a malicious package with a similar name were installed, this command could execute arbitrary code. Although used with `--help` here, it normalizes the use of `npm run` in a troubleshooting context, which is a powerful command execution vector. If the intent is solely to check the version or get help, prefer safer commands like `clawhub --version` or `clawhub --help` directly, or `npm view clawhub version`. If `npm run` is necessary, ensure the package is trusted and its scripts are reviewed for malicious content. | LLM | SKILL.md:64 |
Scan History
Embed Code
[](https://skillshield.io/report/ca8455789d0926d9)
Powered by SkillShield