Trust Assessment
genlayer-dev received a trust score of 78/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, 4 medium, and 0 low severity. Key findings include Missing required field: name, Unpinned dependency 'py-genlayer:latest' used in contract examples.
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 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
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/acastellana/genlayer-dev/SKILL.md:1 | |
| MEDIUM | Unpinned dependency 'py-genlayer:latest' used in contract examples The example GenLayer contracts specify 'py-genlayer:latest' as a dependency. Using unpinned dependencies can introduce supply chain risks, as new versions might contain breaking changes, bugs, or even malicious code without explicit review. For production systems, it is best practice to pin dependencies to exact versions. Pin dependencies to exact versions (e.g., 'py-genlayer:1.2.3') instead of using 'latest' to ensure reproducibility and prevent unexpected changes or vulnerabilities from being introduced. | LLM | SKILL.md:10 | |
| MEDIUM | Unpinned dependency 'py-genlayer:latest' used in contract examples The example GenLayer contracts specify 'py-genlayer:latest' as a dependency. Using unpinned dependencies can introduce supply chain risks, as new versions might contain breaking changes, bugs, or even malicious code without explicit review. For production systems, it is best practice to pin dependencies to exact versions. Pin dependencies to exact versions (e.g., 'py-genlayer:1.2.3') instead of using 'latest' to ensure reproducibility and prevent unexpected changes or vulnerabilities from being introduced. | LLM | SKILL.md:31 | |
| MEDIUM | Unpinned dependency 'py-genlayer:latest' used in contract examples The example GenLayer contracts specify 'py-genlayer:latest' as a dependency. Using unpinned dependencies can introduce supply chain risks, as new versions might contain breaking changes, bugs, or even malicious code without explicit review. For production systems, it is best practice to pin dependencies to exact versions. Pin dependencies to exact versions (e.g., 'py-genlayer:1.2.3') instead of using 'latest' to ensure reproducibility and prevent unexpected changes or vulnerabilities from being introduced. | LLM | SKILL.md:50 |
Scan History
Embed Code
[](https://skillshield.io/report/314e612a0bc12f73)
Powered by SkillShield