Trust Assessment
portfolio-risk-analyzer received a trust score of 10/100, placing it in the Untrusted category. This skill has significant security findings that require attention before use in production.
SkillShield's automated analysis identified 8 findings: 3 critical, 1 high, 3 medium, and 1 low severity. Key findings include Arbitrary command execution, Missing required field: name, Unpinned npm dependency version.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. The Manifest Analysis layer scored lowest at 40/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 Findings8
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Arbitrary command execution Node.js child_process require Review all shell execution calls. Ensure commands are static (not built from user input), use absolute paths, and are strictly necessary. Prefer library APIs over shell commands. | Manifest | skills/kellyclaudeai/portfolio-risk-analyzer/server.js:252 | |
| CRITICAL | Arbitrary command execution Node.js synchronous shell execution Review all shell execution calls. Ensure commands are static (not built from user input), use absolute paths, and are strictly necessary. Prefer library APIs over shell commands. | Manifest | skills/kellyclaudeai/portfolio-risk-analyzer/server.js:253 | |
| CRITICAL | Private Key Exposure via Environment Variable The skill explicitly instructs the user to set a `PAYMENT_WALLET_KEY` environment variable with their private key. This private key is then implicitly used by the skill's scripts (e.g., `uniswap-swap.js` called by `execute-buyback.sh`) to sign blockchain transactions. Storing private keys directly in environment variables is a critical security risk, as they can be easily exposed through process listings, logs, or if the environment is compromised, leading to potential loss of funds. Avoid storing private keys directly in environment variables. Implement secure key management practices such as using hardware security modules (HSMs), cloud key management services (KMS), or encrypted vaults that require explicit authorization for each use. If direct access is unavoidable, use a dedicated, highly restricted wallet with minimal funds for this specific purpose. | LLM | SKILL.md:79 | |
| HIGH | Unpinned Dependencies in package.json The `package.json` file uses caret (`^`) ranges for all dependency versions (e.g., `"express": "^4.18.2"`). This allows `npm` to automatically install newer minor or patch versions. While convenient, it introduces a supply chain risk where a malicious update to a dependency could be pulled in without explicit review, potentially compromising the skill's integrity and security. Pin exact versions for all dependencies (e.g., `"express": "4.18.2"`) to ensure deterministic builds and prevent unexpected updates. Regularly audit and manually update dependencies. Ensure `package-lock.json` is committed and used for deployments to guarantee consistent dependency installations. | LLM | package.json:13 | |
| MEDIUM | Missing required field: name The 'name' field is required for openclaw skills but is missing from frontmatter. Add a 'name' field to the SKILL.md frontmatter. | Static | skills/kellyclaudeai/portfolio-risk-analyzer/SKILL.md:1 | |
| MEDIUM | Unpinned npm dependency version Dependency 'express' is not pinned to an exact version ('^4.18.2'). Pin dependencies to exact versions to reduce drift and supply-chain risk. | Dependencies | skills/kellyclaudeai/portfolio-risk-analyzer/package.json | |
| MEDIUM | API Key Exposure in RPC URLs via Environment Variables The skill instructs users to set environment variables for RPC endpoints (e.g., `ETHEREUM_RPC`) which are expected to contain sensitive API keys (e.g., Alchemy keys). These keys are loaded by `server.js` and used to interact with blockchain networks. While this is a common configuration pattern, it means sensitive API keys are present in the environment where the skill runs, creating a data exfiltration risk if the skill or its host environment were compromised. Treat API keys as sensitive credentials. Ensure the environment running the skill is highly secured and isolated. Consider using dedicated API key management services or role-based access for cloud-hosted RPCs where possible, rather than embedding keys directly in URLs. Implement strict logging and monitoring for API key usage to detect unauthorized access or exfiltration attempts. | LLM | SKILL.md:74 | |
| LOW | Node lockfile missing package.json is present but no lockfile was found (package-lock.json, pnpm-lock.yaml, or yarn.lock). Commit a lockfile for deterministic dependency resolution. | Dependencies | skills/kellyclaudeai/portfolio-risk-analyzer/package.json |
Scan History
Embed Code
[](https://skillshield.io/report/38ccb94813d29e75)
Powered by SkillShield