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
Quality
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 well-crafted skill description that excels across all dimensions. It clearly specifies concrete security hardening actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and is highly distinctive due to the OpenClaw product focus and specific deployment contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, version status checks' - these are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Host security hardening and risk-tolerance configuration for OpenClaw deployments') and when ('Use when a user asks for security audits, firewall/SSH/update hardening...') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'security audits', 'firewall', 'SSH', 'hardening', 'risk posture', 'exposure review', 'cron scheduling', 'version status', plus specific deployment contexts like 'laptop, workstation, Pi, VPS'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the 'OpenClaw' product name as a clear differentiator, combined with specific security hardening context and deployment targets (Pi, VPS). Unlikely to conflict with generic security or system administration 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-structured, actionable skill with excellent workflow clarity and explicit validation checkpoints. The sequential steps, required confirmations, and verification phase demonstrate strong operational safety. However, the document is lengthy and could be more concise by removing some redundancy and splitting detailed reference material into separate files.
Suggestions
Extract OS-specific command references (Linux vs macOS vs Windows checks) into a separate COMMANDS.md reference file to reduce main document length
Consolidate repeated instructions about numbered choices into a single formatting note at the top rather than restating throughout
Consider moving the detailed risk profile descriptions to a separate PROFILES.md file, keeping only brief summaries in the main workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated mentions of numbered choices, multiple reminders about not inventing CLI flags). Some sections could be tightened, though it generally avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides specific, executable commands throughout (e.g., `openclaw security audit --deep`, `ss -ltnup`, `tmutil status`). Commands are copy-paste ready with clear flags and OS-specific variants. | 3 / 3 |
Workflow Clarity | Excellent sequential workflow (steps 0-8) with explicit validation checkpoints (step 8 verify), required confirmations section, and clear feedback loops (re-run audits after changes). Includes rollback considerations and access-preservation strategy. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document (~200 lines) that could benefit from splitting detailed reference material (e.g., OS-specific commands, risk profiles) into separate files. References one external doc but doesn't leverage progressive disclosure fully. | 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
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.