healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
91
88%
Does it follow best practices?
Impact
95%
2.11xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates specific capabilities, provides explicit trigger guidance via a 'Use when...' clause, and includes a rich set of natural keywords users would employ. The OpenClaw-specific context and enumeration of concrete actions (firewall, SSH, cron scheduling, version checks) make it both distinctive and actionable for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: security audits, firewall/SSH/update hardening, risk posture configuration, exposure review, cron scheduling for periodic checks, and version status checks. These are clearly defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (host security hardening and risk-tolerance configuration for OpenClaw deployments) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'security audits', 'firewall', 'SSH', 'hardening', 'risk posture', 'exposure review', 'cron scheduling', 'version status', 'OpenClaw', plus device types like 'laptop', 'workstation', 'Pi', 'VPS'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'OpenClaw' product context combined with host-level security hardening. The combination of OpenClaw-specific features (cron scheduling, version checks) with security hardening creates a clear niche unlikely to conflict with generic security or deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, highly actionable skill with excellent workflow clarity and explicit validation/confirmation checkpoints throughout. Its main weakness is length—it could be more concise by trimming redundant explanations (e.g., the model self-check, repeated notes about what OpenClaw doesn't do) and splitting detailed sections (memory writes, cron scheduling, logging) into referenced sub-files. The actionability and safety guardrails are strong.
Suggestions
Extract the 'Memory writes', 'Logging and audit trail', and 'Periodic checks' sections into separate referenced files to improve progressive disclosure and reduce the main skill's token footprint.
Remove redundant statements (e.g., 'It does not change host firewall, SSH, or OS update policies' appears in multiple forms) and consolidate the model self-check into a single brief note rather than a full workflow step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~200+ lines) and includes some unnecessary elaboration (e.g., listing non-technical prompt examples verbatim, explaining what --fix does/doesn't do multiple times, the model self-check section). However, most content is task-specific and not explaining concepts Claude already knows, so it's not egregiously verbose. | 2 / 3 |
Actionability | The skill provides specific, executable commands throughout (e.g., `openclaw security audit --deep`, `ss -ltnup`, `sw_vers`, `tmutil status`, `openclaw cron add --name healthcheck:security-audit`). It includes exact CLI flags, OS-specific command variants, and concrete numbered options for user interaction. The guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (steps 0-8) with explicit validation checkpoints (step 8 re-checks firewall, ports, access, and re-runs audit). It includes feedback loops (stop on unexpected output), rollback planning, access-preservation strategy, and required confirmations for all destructive/state-changing operations. The cron scheduling section includes idempotency checks (list before add/edit). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and numbered steps, but it's a monolithic document with no references to external files for detailed content. The risk profiles, periodic checks, memory writes, and logging sections could be split into separate reference files. The one reference to `docs/reference/templates/AGENTS.md` is appropriate but the skill itself is quite long for a single file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.