Capture website screenshots from the command line. Use when user wants to take screenshots of any URL (Twitter, news sites, webpages) and send them via Disco...

This skill is plausible for taking screenshots, but it has gaps and assumptions you should address before installing or allowing it to run: 1) The SKILL.md requires 'npm install -g capture-website-cli' but the skill metadata doesn't declare node/npm—confirm that installing a global npm package is acceptable and verify the package source (review the npm package and its maintainer). 2) The instructions use a hard-coded path (/home/aaronz/.openclaw/workspace/) — ensure the skill will use a sandboxed or canonical workspace path rather than assuming another user's home directory. 3) The README mentions sending via Discord/Feishu but doesn't declare or request tokens; confirm what messaging tool the agent will actually use and how credentials are provided/secured to avoid unintended data exfiltration. 4) Be aware a screenshot tool will fetch arbitrary URLs; if your agent can access internal networks, this could be used to capture internal pages (SSRF-like data exposure). 5) Prefer an explicit install spec (or containerized runtime) and explicit required binaries/permissions in the skill metadata. If you rely on this skill, ask the author to: add required binaries (node/npm), include an install specification or trusted source for the CLI, remove hard-coded paths in favor of workspace variables, and declare any message-sending credentials and their intended use. If you cannot verify the CLI package or these changes, treat execution as higher risk.

Type: OpenClaw Skill Name: capture-website Version: 1.0.0 The skill is classified as suspicious due to two main factors found in `SKILL.md`. First, it instructs the agent to perform a global npm package installation (`npm install -g capture-website-cli`), which introduces a supply chain risk by executing arbitrary code from a public registry. Second, the skill executes a shell command (`capture-website <URL>`) with a user-provided URL, creating a potential shell injection vulnerability if the agent does not adequately sanitize the input URL before execution. While these actions are plausibly needed for the skill's stated purpose, they represent significant risky capabilities and vulnerabilities, respectively, without clear evidence of intentional malicious exploitation by the skill itself.