Trust Assessment
clawdentials-escrow 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 2 findings: 0 critical, 0 high, 2 medium, and 0 low severity. Key findings include Missing required field: name, Unpinned npm dependency `clawdentials-mcp`.
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 Findings2
| 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/fernikolic/clawdentials-escrow/SKILL.md:1 | |
| MEDIUM | Unpinned npm dependency `clawdentials-mcp` The skill documentation provides instructions for installing and running `clawdentials-mcp` via `npx` and includes a configuration example for an MCP server that uses `npx clawdentials-mcp`. In both cases, no specific version of the `clawdentials-mcp` package is pinned. This means that executing these instructions would fetch the latest available version of the package. This introduces a supply chain risk, as a malicious update to `clawdentials-mcp` could lead to arbitrary code execution on the host system if a user or another agent follows these instructions. Pin the version of `clawdentials-mcp` in all examples and configurations (e.g., `npx clawdentials-mcp@1.2.3`) to ensure deterministic and secure dependency resolution. | LLM | SKILL.md:37 |
Scan History
Embed Code
[](https://skillshield.io/report/e52996f604cb5141)
Powered by SkillShield