healthcheck — Claude Code skill: what it does, how to install
Audits OpenClaw host security, listening ports, SSH, and firewalls. Spots exposures and applies staged hardening without locking you out.
npx skills add openclaw/openclaw --skill healthcheck -a claude-codeWhat healthcheck does
The skill inspects host security, checking privilege levels and access paths. Diagnosis comes first. The tool runs read-only commands like openclaw security audit --deep and openclaw doctor --lint. It also inspects active firewall rules, disk encryption, and listening sockets on Linux, macOS, or Windows.
After reporting the findings, the agent suggests a hardening posture from low friction to strict lockdown. It never touches SSH settings, firewall rules, or gateway bindings without explicit approval for each change. This prevents accidental lockouts during remote sessions.
Install this skill if you run OpenClaw on a workstation or remote server and want to lock down the gateway. For isolated disposable containers, skip it.
What it helps with
- audit listening ports and network exposure
- verify disk encryption and backup status
- bind the OpenClaw gateway safely to local or tailnet interfaces
- harden SSH access and firewall rules without dropping connections
Example prompts for the agent
- Run a security audit on this host
- Check firewall status and OpenClaw gateway binding
- Help me close exposed ports safely
How to install healthcheck
1Skills CLI (Vercel)
npx skills add openclaw/openclaw --skill healthcheck -a claude-code2Manually: put the files in place
~/.claude/skills/healthcheck/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/healthcheck/
1Skills CLI (Vercel)
npx skills add openclaw/openclaw --skill healthcheck -a codex2Manually: put the files in place
.agents/skills/healthcheck/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openclaw/openclaw --skill healthcheck -a cursor2Manually: put the files in place
.cursor/skills/healthcheck/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openclaw/openclaw healthcheck2Manually: put the files in place
.github/skills/healthcheck/SKILL.md1Skills CLI (Vercel)
npx skills add openclaw/openclaw --skill healthcheck -a gemini-cli2Platform CLI
gemini skills install https://github.com/openclaw/openclaw --path skills/healthcheckManually: put the files in place
.devin/skills/healthcheck/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add openclaw/openclaw --skill healthcheck -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set45
The whole set →Similar
Questions about healthcheck
How do I install healthcheck in Claude Code?
Run npx skills add openclaw/openclaw --skill healthcheck -a claude-code in your terminal. This configures the skill inside ~/.claude/skills/healthcheck/SKILL.md.
What does the healthcheck skill do?
It inspects your host system and OpenClaw configuration using read-only checks. Then it reports security findings and outlines staged hardening steps.
Can this skill lock me out of my remote server?
No. The skill is instructed never to modify SSH or firewall settings without confirming the access path first, and every state change requires direct approval.
Source text
SKILL.md · MIT
--- name: healthcheck description: "Audit/harden OpenClaw hosts: SSH, firewall, updates, exposure, backups, disk encryption, gateway security." --- # OpenClaw host healthcheck Goal: assess host risk, run read-only checks, then propose staged hardening without breaking access. ## Rules - Ask before state-changing actions. - Do not change SSH/firewall/remote access until access path is confirmed. - Prefer reversible steps and rollback notes. - Never claim OpenClaw manages OS firewall, SSH, or updates. - If identity/role unknown, recommend only. - User choices: numbered list. - Never print secrets. ## Context to infer first - OS/version, container vs host. - Privilege level. - Access path: local, SSH, RDP, tailnet. - Network exposure: public IP, reverse proxy, tunnel, LAN only. - OpenClaw gateway status, bind, auth. - Backup status. - Disk encryption. - Automatic security updates. - Usage mode: personal workstation, local assistant box, remote server, other. Ask only for missing facts. Simple phrasing preferred. ## Read-only checks Ask once for permission to run read-only checks. Then run relevant commands. Common: ```bash openclaw security audit --deep openclaw gateway status --deep openclaw doctor --lint ``` `doctor --lint` can exit `1` for findings: read the report and continue the remaining checks. Ordinary `doctor` and `doctor --non-interactive` can copy legacy config and migrate state without `--fix`; reserve repairs for explicit approval. Read-only checks exclude config/service repairs and state migrations, but may produce incidental logs or cache bookkeeping. macOS: ```bash sw_vers lsof -nP -iTCP -sTCP:LISTEN /usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate pfctl -s info tmutil status fdesetup status softwareupdate --schedule ``` Linux: ```bash cat /etc/os-release ss -ltnup || ss -ltnp ufw status || firewall-cmd --state || nft list ruleset systemctl status ssh sshd lsblk -f ``` Windows: ```powershell systeminfo Get-NetFirewallProfile Get-BitLockerVolume ``` ## Risk profile After context is known, ask desired posture: 1. Convenience: local/private, minimal prompts. 2. Balanced: secure defaults, low friction. 3. Strict: remote/public/sensitive data, more lock-down. ## Report shape - Current posture: one paragraph. - Findings: severity + evidence + why it matters. - Recommended plan: staged, reversible. - Commands: read-only first; write actions only after approval. - Gaps: what could not be checked. ## Hardening menu Offer only relevant items: - Bind gateway to loopback/LAN/tailnet intentionally. - Require auth for remote access. - Close public ports or restrict by firewall. - Enable OS security updates. - Enable disk encryption. - Verify backups and restore path. - Disable password SSH or require keys/MFA where appropriate. - Add scheduled `openclaw security audit --deep`. Confirm exact action before applying.
© openclaw · MIT · openclaw/openclaw