BC openclaw-macos-security
macOS security monitoring for OpenClaw
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityREADME.md:92Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- `keylogger-detector` - Keylogger scan
detector -
low Risky intent
intent-offensive-securityskill-card.md:21Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Mitigation: Review before installing, treat results as narrow local status checks, and do not rely on the skill for app removal, keylogger/rootkit detection, or broad macOS protection unless those fea
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 642 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 38: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -215 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This skill is not malware-like, but it materially overstates its macOS security capabilities while requesting local command-execution permissions.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026