OpenClaw PC Security

Description

Security self-check and risk alerting for:

• - Windows baseline (version/build, last security update date, support status, patch lag)
• Local OpenClaw CLI version vs latest (optional online check)
• OpenClaw server configuration safety (password protection, default port use, public exposure)
• Optional OpenClaw target checks (authorized use only)

When to use

Use this skill when you need to:

• - Check whether Windows is out of support or significantly behind updates
• Confirm whether OpenClaw is up to date on your machine
• If you deployed OpenClaw on a VPS/personal server, verify the setup is safe (password protection on, avoid default port, restrict exposure)
• Generate a local HTML/JSON report for your own reference (do not upload publicly)

Input

• - Local machine information (Windows version/build, last update date)
• Optional OpenClaw config file path for server-side checks (e.g., config.json)
• Optional target host/IP and ports for OpenClaw probing (authorized environments only)

Output

• - Severity-based findings (Info/Medium/High/Critical)
• HTML/JSON report under INLINECODE0

• - Finding types include:

Steps

1) Local audit

Optional: if you know your OpenClaw config file path:
CODEBLOCK1

2) Scan a target (authorized environments only)

Optional: enable active checks explicitly (disabled by default)
CODEBLOCK3

Notes

• - The server configuration checks are performed locally and do not send data to external services.
• The HTML report supports CN/EN toggle and Simple/Detailed mode.
• Active network checks must ONLY be used on systems you own or have explicit authorization to test.
• DO NOT upload tokens, credentials, or reports (output/) to public repositories.
• Reports are written under output/ when using the provided scripts.
• If OpenClaw is outdated: after upgrading, some or all functions may be unavailable; assess carefully.
• After the HTML report is generated, print the report path in the chat for the user's reference. Do NOT upload or send the report file unless the user explicitly requests it and provides a secure destination. Reports may contain sensitive information, so always handle them with caution.