Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AI Screen Vision
v1.0.6AI screen vision and desktop computer control skill for OpenClaw. Let your AI agent see the screen, understand UI elements, and autonomously perform mouse an...
⭐ 0· 50·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
The code and scripts align with a screen-vision / desktop-automation purpose (screenshots, vision API calls, xdotool/cliclick/pyautogui). However the registry metadata claims no required env vars or binaries, while the skill clearly expects an API key (SV_VISION_API_KEY / config.json) and platform tools. The default network endpoint (SV_VISION_BASE_URL=https://api.gpt.ge/v1) is nonstandard and surprising as a default provider.
Instruction Scope
Runtime instructions and scripts perform wide system actions: take screenshots, save logs to /tmp, call an external vision API with base64-encoded screenshots, and execute arbitrary mouse/keyboard events. Setup scripts instruct installing desktop environments, creating VNC/noVNC services, and granting macOS accessibility/screen-recording permissions. These steps are within the claimed feature set but also expand scope to remote desktop exposure and system-level service configuration (VNC/noVNC).
Install Mechanism
Installation runs system package installs (apt/yum/dnf), pip installs, and writes files to ~/.openclaw, ~/.vnc and /usr/local/bin (sv-start / sv-stop). While packages come from OS package managers (not arbitrary downloads), the script configures a VNC/noVNC stack and uses a hardcoded/default VNC password (screen123) in the provided script — this creates a network-accessible surface and persistent system services.
Credentials
The skill requires and reads SV_VISION_API_KEY, SV_VISION_BASE_URL, SV_VISION_MODEL and supports config.json, but the registry metadata lists no required env vars/primary credential — a mismatch. Sending full screenshots to an external API is expected for vision, but the default base URL points to an unfamiliar domain (api.gpt.ge) instead of a well-known provider, which is unexpected and should be verified before use.
Persistence & Privilege
The skill does not set always:true, but installation creates persistent artifacts and system scripts (VNC start/stop, ~/.vnc/password, /usr/local/bin/sv-start) and may expose a desktop via noVNC/websockify. That increases the blast radius if the skill is later invoked autonomously — combined with networked screenshot uploads and logs in /tmp, this is a material privilege and exposure change to the host.
What to consider before installing
Key things to consider before installing:
- Verify the vision API endpoint and provider: the default SV_VISION_BASE_URL is https://api.gpt.ge/v1 (not an obvious official host). If you plan to use a cloud provider, set the base URL and API key to a provider you trust (OpenAI/Azure/Google) or use a local model.
- Treat screenshots as sensitive: the skill base64-encodes and uploads full-screen images to the configured API. Only use with a trusted vision endpoint and avoid running on machines with sensitive information on screen.
- Review and modify VNC/noVNC behavior: headless setup creates a VNC server and a noVNC web front-end and sets a default VNC password in install scripts. Change any default password, restrict access (bind to localhost or use firewall rules), or skip the headless/noVNC setup if you don't need remote web access.
- Review system changes and run in isolation: the installer uses sudo to install packages and writes to /usr/local/bin and ~/.vnc. Consider testing in a disposable VM/container with restricted network access first.
- Confirm safety policy limits: the skill includes safety_check logic, but it uses some hard-coded patterns and limits; review it to ensure it blocks actions you consider dangerous (customize confirm_before/blocked patterns as needed).
- Metadata mismatch: registry metadata lists no required env vars, but the code uses SV_VISION_API_KEY and config.json; ensure the platform supplies those securely and that you understand where secrets are stored.
If you decide to proceed: run the setup manually and inspect the scripts (setup scripts, sv-start content, config.json) before executing; avoid the headless/noVNC path unless you harden access and change the default password; and prefer a local vision model or a vetted cloud endpoint for image uploads.Like a lobster shell, security has layers — review code before you run it.
latestvk973q3vdkh10vq7c3r4650pn8n8492m5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
