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 the domain (OpenClaw security hardening), lists concrete actions, provides explicit 'Use when' triggers with natural user terminology, and maintains distinctiveness through product-specific context and deployment scenarios.
| 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 clear workflows and proper validation checkpoints for security-sensitive operations. The main weakness is length—it could be more concise by removing redundant instructions and splitting detailed reference material into separate files. The explicit confirmation requirements and rollback planning demonstrate good safety practices.
Suggestions
Extract OS-specific command references (Linux vs macOS checks) into a separate COMMANDS.md file to reduce main skill length
Consolidate repeated instructions about numbered choices and explicit approval into a single 'Interaction rules' section rather than restating throughout
Move the detailed risk profile descriptions to a separate PROFILES.md file, keeping only brief summaries in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeated numbered choice formatting instructions, multiple mentions of requiring explicit approval). Some sections like the memory writes and logging could be tightened. | 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 with numbered steps (0-8), explicit validation checkpoints (step 8 re-checks), rollback considerations, and clear confirmation requirements. The verify-and-report step provides proper feedback loops. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~200 lines) and could benefit from splitting detailed reference material (e.g., OS-specific commands, risk profiles) into separate files. Currently monolithic despite good internal structure. | 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.
50ef2f3
Table of Contents
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.