How do I install the Healthcheck skill?

Run npx skillmds@latest add openclaw/healthcheck in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Healthcheck safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Healthcheck?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Healthcheck free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Healthcheck?

OpenClaw (@openclaw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Healthcheck by openclaw — Agent Skill

Name: Healthcheck
Rating: 4.5 (4 reviews)
Author: OpenClaw

File contents

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:

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:

sw_vers
lsof -nP -iTCP -sTCP:LISTEN
/usr/libexec/ApplicationFirewall/socketfilterfw --getglobalstate
pfctl -s info
tmutil status
fdesetup status
softwareupdate --schedule

Linux:

cat /etc/os-release
ss -ltnup || ss -ltnp
ufw status || firewall-cmd --state || nft list ruleset
systemctl status ssh sshd
lsblk -f

Windows:

systeminfo
Get-NetFirewallProfile
Get-BitLockerVolume

Risk profile

After context is known, ask desired posture:

Convenience: local/private, minimal prompts.
Balanced: secure defaults, low friction.
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.

---name: healthcheckdescription: 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.

Frequently asked questions

Healthcheck