sshot
The skill delegates execution to an opaque external PowerShell script that is not included in the package, creating an unauditable blind spot where undeclared behavior could occur without being detected.
Why this conclusion was reached
1/4 dimensions flaggedDeclared resources and inferred behavior are broadly aligned.
No obvious high-risk egress or execution signals were found.
The report includes 3 attack-chain steps and 1 severe findings.
Dependency information is incomplete, so supply-chain confidence stays limited.
Attack Chain
Entry · SKILL.md:1
Escalation · SKILL.md:11
Impact · External: sshot.ps1
What drove the risk score up
The skill defers all logic to C:\Users\AlenZhu\.openclaw\scripts\sshot.ps1 which is not included in the package, preventing any code audit
Path C:\Users\AlenZhu\.openclaw\scripts\sshot.ps1 contains a specific username, suggesting a targeted deployment that is not portable and could be leveraged for user-specific targeting
Only SKILL.md and meta.json are present; no scripts, source code, or dependencies to verify the actual behavior described
PowerShell -ExecutionPolicy Bypass can disable security policies, increasing the impact if the external script is malicious
Most important evidence
Critical script artifact not included in package
The SKILL.md declares behavior as 'take full screen screenshot' but delegates all implementation to an external PowerShell script (C:\Users\AlenZhu\.openclaw\scripts\sshot.ps1) that is not included in this package. There is no source code, script, or dependency file to audit the actual behavior of the skill. The skill's true behavior is entirely opaque.
SKILL.md:11 Hardcoded user-specific path in skill definition
The script path references a specific Windows user profile (C:\Users\AlenZhu\.openclaw\scripts\sshot.ps1). This indicates the skill was authored for a single targeted machine rather than being portable. An attacker controlling this path or compromising the referenced location could replace the script with malicious code.
SKILL.md:11 ExecutionPolicy Bypass weakens PowerShell security controls
The -ExecutionPolicy Bypass flag disables PowerShell script signing and execution policy requirements. While this is sometimes legitimate for automation scripts, it is not mentioned or justified in the documentation. Combined with the unauditable external script, this increases risk.
SKILL.md:10 Declared capability vs actual capability
SKILL.md:11 - system.run on node External script sshot.ps1 not provided; behavior cannot be audited External script sshot.ps1 not provided; network behavior cannot be audited Suspicious artifacts and egress
No obvious IOC was extracted.
Dependencies and supply chain
There are no structured dependency warnings.
File composition
SKILL.md