Security Audit

polymarket

github.com/openclaw/skills

AI SkillCommit 13146e6a3d46

CAUTION

Scanned about 2 months ago

Critical

Immediate action required

High

Priority fixes suggested

Medium

Best practices review

Low

Acknowledged / Tracked

Trust Assessment

polymarket 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 1 finding: 1 critical, 0 high, 0 medium, and 0 low severity. Key findings include Unverified/Unpinned Executable Download Instruction.

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

Manifest Analysis

100%

Static Code Analysis

100%

Dependency Graph

100%

LLM Behavioral Safety

70%

Behavioral Risk Signals

Network Access

1 finding

Filesystem Write

1 finding

Shell Execution

1 finding

Security Findings1

Severity	Finding	Layer	Location
CRITICAL	Unverified/Unpinned Executable Download Instruction The skill instructs users to download and run an executable (`openclawcli`) from an unpinned `latest` GitHub release URL and a `glot.io` snippet. This poses a significant supply chain risk as the content of these downloads can change at any time, potentially introducing malicious code. The use of a hardcoded password (`openclaw`) for the zip file further indicates a non-standard and potentially insecure distribution method, making it difficult for users to verify the integrity and authenticity of the software. 1. Pin dependencies: Provide a specific version hash or commit SHA for `openclawcli` downloads instead of using a mutable `latest` tag. 2. Trusted distribution: Distribute `openclawcli` through a more trusted and verifiable channel (e.g., official package manager, signed binaries, or a dedicated, secure download page with checksums). 3. Remove `glot.io` link: Replace the `glot.io` link with a secure, version-controlled installation method. 4. Remove hardcoded password: Avoid hardcoding passwords for archives; use secure distribution methods that don't require this.	LLM	SKILL.md:9

Scan History

Embed Code

[![SkillShield](https://skillshield.io/api/v1/badge/1dab5e235f18e6fd.svg)](https://skillshield.io/report/1dab5e235f18e6fd)