Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
PCClaw
v2.0.0PCClaw provides 16 native Windows AI skills for system control, automation, files, notifications, OCR, speech, LLM inference, and task management with minima...
⭐ 0· 436·2 current·2 all-time
by@lmanchu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The set of per-skill instructions (win-clipboard, win-screenshot, win-ocr, win-browser, sticky-notes, win-files, win-ai-local, etc.) align with the name/description: they use Win32/.NET/WMI/WinRT and local tools to inspect and control a Windows system. Cross-platform skills (ms-todo, google-tasks) appropriately document OAuth flows or CLI backends.
Instruction Scope
Most SKILL.md files stay within expected scope (reading Sticky Notes DB, browser bookmarks/history, invoking Ollama locally, managing Task Scheduler). However the top-level README/SKILL.md instructs running a remote installer that 'Registers on Moltbook — Creates your AI agent profile and posts first message' and 'Configures your LLM' — network activity and automatic account creation/posting are scope creep relative to a purely-local skills bundle and may transmit metadata or create external traces. Several skills read sensitive local data (browser history, bookmarks, sticky notes) — this is coherent with purpose but privacy-sensitive and should be explicit to users.
Install Mechanism
There is no formal install spec in the registry, but the README strongly recommends running a one-liner: irm openclaw.irisgo.xyz/i | iex. Piping a remote PowerShell script to iex downloads and executes arbitrary remote code; the script is not included here for inspection. That pattern is high-risk because it gives the remote host immediate code-execution capability on the user's machine. A manual installation alternative is shown, which is safer if the user inspects files first.
Credentials
Top-level metadata lists no required env vars, which matches the registry. Individual skill docs correctly document per-skill requirements (e.g., ms-todo requires MS_TODO_CLIENT_ID and MS_TODO_REFRESH_TOKEN; google-tasks documents OAuth client_id/secret or gog CLI). These per-skill credentials are appropriate for their functions. The README's BYOK claim ('We never collect or transmit it') is a positive statement but cannot be verified from the instruction-only content; the installer’s Moltbook registration and 'Configure your LLM' steps raise the possibility of network-transmitted metadata or tokens if the installer script does so.
Persistence & Privilege
always: false (no forced permanent inclusion). The README/installer will install system-wide components if used (Node.js, npm global openclaw@latest, copy skills into %USERPROFILE%\.openclaw, create %USERPROFILE%\.config\moltbook\credentials.json). That means the installer can create persistent files and register external accounts, but the skill bundle itself (as published here) does not request elevated privileges or an always-on presence. Users should expect the installer to modify their system and create stored credentials if they run it.
What to consider before installing
This package mostly does what it says: many skills intentionally read local Windows data (Sticky Notes DB, browser bookmarks/history, filesystem, task scheduler) and call local LLMs (Ollama) or OAuth flows for cloud task services. The main red flags are the recommended one-liner installer (irm openclaw.irisgo.xyz/i | iex) — piping remote PowerShell into iex executes unreviewed code — and the installer’s automatic Moltbook registration/posting behaviour (network activity you may not expect). Before installing: 1) Do not run the one-liner unless you trust and have inspected the remote script. 2) Prefer manual install: download the repository and inspect install.ps1/i script contents. 3) Verify what the installer will send to external services (Moltbook) and whether API keys or other data are transmitted. 4) If you are privacy-conscious, run in an isolated VM or test machine first. 5) Review and back up any local data (browser profiles, Sticky Notes DB) before allowing tools that read them. If you want help reviewing the remote installer script (openclaw.irisgo.xyz/i) or the specific installer steps, provide the script and I can analyze it for unexpected network calls or data exfiltration.Like a lobster shell, security has layers — review code before you run it.
latestvk97bphhq4pcfp9wcfda6hpjs9s81xcfc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.