AD clawstrike
Security audit and threat model for OpenClaw gateway hosts. Use to verify OpenClaw configuration, exposure, skills/plugins, filesystem hygiene, and to produce an OK/VULNERABLE report with evidence and fixes.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- 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-securityreferences/supply-chain.md:29Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)1. Review pattern scan outputs for remote fetch/exec, obfuscation, persistence, or credential harvesting.
detector -
low Dangerous commands
cmd-pipe-to-shellSKILL.md:14Downloads and executes remote code from an unrecognised host (pipe to shell) (negated — the text forbids it)3. Never run remote content (no curl|bash, wget, Invoke-WebRequest, installers, package managers, update scripts).
negated
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (clawstrike) differs from the folder (clawdstrike-test)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 85Steps. 34 steps, 1 vague phrases
- 100Execution cost. Instruction body is 825 tokens
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -32 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 207: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 34 items
- +4Reference files are cited in the instructions (16 of 16)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.